chore: publish version 2025-1-RC1
#131
Merged
Conversation
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
jimmarino
approved these changes
Feb 27, 2025
juliapampus
approved these changes
Feb 27, 2025
There was a problem hiding this comment.
Won't commit d8f6428 be invalid if we squash and merge?
So shouldn't we merge this one with the "RC1" in the titles in index.html, then create a tag, and after that create a new pull request updating the index.html?
We plan rebase and merge |
ssteinbuss
merged commit 9bac6a0
into
eclipse-dataspace-protocol-base:main
2 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR changes/adds
This PR publishes a separate github page for the current state of the spec as a first Release Candidate for version
2025-1.Why it does that
Lots of new features.
Further notes
There is further action required from the committer who merges this PR.
Github does not allow to merge tags via PRs. Every committer however can push tags to main. After merging this PR, a committer must:
2025-1-RC1on commit d8f6428a1b7a9a9be13719c226eaa8d9cbb5adc9 and push if done in IDE.This will lead to a setup like in my fork:
https://arnoweiss.github.io/DataspaceProtocol/
https://arnoweiss.github.io/DataspaceProtocol/2025-1-RC1/
https://arnoweiss.github.io/DataspaceProtocol/HEAD/