Repository navigation
release v4.2.4 - #2041
Open
bplatz wants to merge 2 commits into
Open
release v4.2.4#2041bplatz wants to merge 2 commits into
bplatz wants to merge 2 commits into
Conversation
# Conflicts: # Cargo.lock # Cargo.toml # testsuite-shacl/Cargo.lock # testsuite-shacl/Cargo.toml # testsuite-sparql/Cargo.lock # testsuite-sparql/Cargo.toml
This branch has not been deployed
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
1 participant
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.
Version bump
4.2.4-beta.1→4.2.4. Tagv4.2.4after this merges tomain.Release notes are generated from merged PR titles at tag time, so the changelog reflects the final contents once this merges and publishes.
Notes for review
This is branched from the current
mainso the bump can be approved ahead of time. The PRs targeted for 4.2.4 will land first, then latestorigin/maingets merged into this branch before it merges. The lockfiles may need a refresh at that point if any of those PRs add or drop dependencies. If #2036 (4.2.4-beta.2) lands first, its version lines conflict with these and resolve to4.2.4.testsuite-sparqlandtestsuite-shaclare workspace-excluded and carry independent versions and lockfiles, hence six files rather than two. All three lockfiles are version lines only, and all three resolve undercargo metadata --locked. The Python package takes its version from the workspace, soflureepublishes to PyPI as 4.2.4 from the same tag.