Open
Conversation
linux-armv6 uses Debian 11, which provides cmake 3.13
- Move all dependency version numbers into a single location - Remove unused integrity calculations, provenance will replace it - Use single POSIX script for Linux and macOS (remove symlink) - Use ARM64 CI runners for linux-arm64v8 and linuxmusl-arm64v8
aom 3.12.1 claims to require cmake 3.16 but seems to build quite happily with cmake 3.13, as provided by Amazon Linux 2.
This moves the release process a step closer to directly publishing packages to the npm registry.
* glib: do not place files outside install prefix * fontconfig: disable install of gettext files * macOS: restore directories removed in 2760713
This will eventually be part of the glib-without-gregex patch
Otherwise RISC-V cross-compilation fails. Can investigate later, ignore for now.
(alternative patch to remove changelog entry)
The new release-monitoring infrastructure (correctly) appears to enforce rate-limiting so sleep a little and switch to checking GitHub tags for projects with sensible versioning history.
Allows use of not-yet-stable flags to reduce binary size by ~200KB Co-authored-by: Kleis Auke Wolthuizen <github@kleisauke.nl>
The latest glib 2.85.2 introduces new code dependent on the deprecated (and patch-removed by us) GRegex.
Author
|
Build failed on 2 latest version checks - one of them (de265) we'll bump ourselves, the other I see a commit to fix from 9h ago on the lovell repo. I can see their pipeline failed from that bump, though... so I am curious to give them a bit more time to follow-up with another commit fixing the failed pipeline, which they tend to do quickly (1-2 days) - should save us from wasting build time to do it that way as we're in no rush 🙂 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bump our libvips to the latest release of lovell's libvips (v1.1.0 -> v1.2.1)
The process to do this was essentially
git fetch --allThen
git cherry-pick <commit sha>every commit since we last updated (release v1.1.0 commit).If I hit a conflict, I ran
git cherry-pick --abort, pushed the "clean" commits, then focused solely on the commit with conflicts.When I felt confident that one, tricky commit was resolved correctly, I'd push the changes.
Rinse, repeat with the remaining commits - until I got to the latest release commit.
I suspect there will be some issues with switching to ci.yml that I'll need to work through...
(I'll rename the branch to main after these updates)