Update version to 4.1.2 and update release instructions #106
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
There was a problem hiding this comment.
Pull Request Overview
This PR updates the release process by removing the conflicting release.yml action and providing revised, manual release instructions for maintainers to follow when cutting a new release.
- Updates version references to 4.1.2.
- Replaces the automated release action with step-by-step manual instructions derived from the go-dependency-submission-action process.
Files not reviewed (2)
- .github/workflows/release.yml: Language not supported
- package.json: Language not supported
Tip: If you use Visual Studio Code, you can request a review from Copilot before you push from the "Source Control" tab. Learn more
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.
The release.yml action violates our branch protection rules, so unfortunately we won't be able to keep using it. Instead, we'll have to copy the release process that we use for the rest of our actions, like https://github.com/actions/go-dependency-submission.
At the same time, I'm following these instructions myself to release 4.1.2.