-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create RELEASE.md #151
Open
RobbenRiksen
wants to merge
1
commit into
main
Choose a base branch
from
RobbenRiksen-patch-1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Create RELEASE.md #151
Conversation
This file contains 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
Added as action discussed in a TSC meeting. Does this need more text? Should we add the text from the TSC release file as well (or do we need to review that one)? Signed-off-by: RobbenRiksen <[email protected]>
KoviaX
reviewed
Feb 28, 2025
@@ -0,0 +1 @@ | |||
With each new major version of the specification, we aim to evaluate and include all dependencies that have a major bump as indicated by Dependabot in the new major release of the specification. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
With each new major version of the specification, we aim to evaluate and include all dependencies that have a major bump as indicated by Dependabot in the new major release of the specification. | |
This file lists the steps involved with creating a new release of the specification: | |
- With each new major version of the specification, we aim to evaluate and include all dependencies that have a major bump as indicated by Dependabot in the new major release of the specification. | |
- Determine breaking changes and write a migration |
nicorikken
reviewed
Feb 28, 2025
@@ -0,0 +1 @@ | |||
With each new major version of the specification, we aim to evaluate and include all dependencies that have a major bump as indicated by Dependabot in the new major release of the specification. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
With each new major version of the specification, we aim to evaluate and include all dependencies that have a major bump as indicated by Dependabot in the new major release of the specification. | |
<!-- | |
SPDX-FileCopyrightText: Contributors to the Shapeshifter project | |
SPDX-License-Identifier: Apache-2.0 | |
--> | |
With each new major version of the specification, we aim to evaluate and include all dependencies that have a major bump as indicated by Dependabot in the new major release of the specification. |
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.
Added as action discussed in a TSC meeting.
Does this need more text? Should we add the text from the TSC release file as well (or do we need to review that one)?