Repository navigation
chore: retire the v0.69.0 release notice - #1362
Merged
Merged
Conversation
.github/RELEASE_NOTICE.md is prepended verbatim to the release body and is written for one release. v0.69.0 has shipped, so it is removed here to stop it repeating on the next release. Opened automatically by .github/workflows/retire-release-notice.yml.
Deploying mcpproxy-docs with
|
| Latest commit: |
e66c21a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://613f0287.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://chore-retire-release-notice-3xs0.mcpproxy-docs.pages.dev |
2 of 3 tasks
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 4, 2026
…#1491) # Pull Request ## Description The v0.70.0 release notes covered only the rc.4 → rc.5 fixes, described the release as "stability improvements", and missed profiles v3, per-client credentials and agent visibility. I rewrote them by hand after the release. **Cause.** `release.yml`'s `generate-notes` job finds the previous tag with `git describe --tags --abbrev=0 HEAD^`. After an RC cycle, the nearest tag is the last RC, so the commit range sent to the summarizer was `v0.70.0-rc.4..v0.70.0`, not `v0.69.0..v0.70.0`. **Fix.** Exclude prerelease tags (`--exclude '*-*'`) when looking up the previous tag: - In `release.yml`, the `generate-notes` job, which runs for stable tags only. - In `scripts/generate-release-notes.sh`, used for local runs: stable tags get the same exclusion, and RC tags keep comparing with the nearest tag of any kind. The release notice problem is separate and not changed here. It comes from the unmerged retire PR #1362. ## Testing - [x] I have tested these changes locally - [ ] I have added/updated tests that prove my fix is effective or my feature works - [x] All existing tests pass `get_previous_tag` against real tags returns: | Tag | Previous tag | |---|---| | `v0.70.0` | `v0.69.0` (was rc.4/rc.5) | | `v0.70.0-rc.5` | `v0.70.0-rc.4` | | `v0.70.0-rc.2` | `v0.70.0-rc.1` | | `v0.69.0` | `v0.68.0` | The workflow expression, simulated at `v0.70.0`, returns `v0.69.0`. `bash -n` and a YAML parse both pass. There is no test harness for the release workflow. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Contributor
Author
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 37176458867 --repo smart-mcp-proxy/mcpproxy-go
|
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Dumbris
approved these changes
Oct 4, 2026
Dumbris
enabled auto-merge (squash)
October 4, 2026 06:07
Dumbris
changed the title
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
2 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.
.github/RELEASE_NOTICE.mdis prepended verbatim to the release body byrelease.yml, and is written for a single release.v0.69.0 has shipped, so the notice is removed here. Without this, the same advisory would repeat on every subsequent release — and a reader who sees the same advisory three times stops believing any of them.
If you want the notice to stay for a follow-up patch release, close this PR; another will be opened after the next published release.
Checks will not start on their own. This PR was opened with
GITHUB_TOKEN, and GitHub does not runpull_requestworkflows for it. Close and reopen the PR, or push an empty commit to the branch, and the required checks will run.Opened automatically by
.github/workflows/retire-release-notice.yml.