Docs: add v3.4.1 changelog entries#4289
Merged
Merged
Conversation
jlowin
added
the
documentation
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.
Adds the
v3.4.1: Floor Itentries to the docs changelog and updates feed, mirroring the GitHub release.It also corrects the release-workflow guidance in
CLAUDE.md: the changelog/updates PR must be merged before the release is tagged, not after. The post-publishupdate-published-docsjob force-pushes thepublished-docsbranch (which gofastmcp.com serves) to the released commit, so a changelog entry only reaches the live site if it's already in the commit being tagged. The old "land the docs PR with or just after the release" ordering silently skipped each release's own changelog entry until the next release advancedpublished-docs.