Repository navigation
docs: date the 3.4.6 CHANGELOG entry with its release day - #544
Merged
Merged
Conversation
Co-Authored-By: Claude <noreply@anthropic.com>
There was a problem hiding this comment.
🟢 Approval recommended
The single documentation change matches the stated release date and follows the documented release process.
No open issues 🎉
What changed in this PR
Updates the core package’s 3.4.6 changelog date to match its stated release day before tagging v3.4.6.
Changes:
- Changes the release date from 2026-10-23 to 2026-10-27; no runtime behavior or package version changes.
| File | Description |
|---|---|
flutter_cache_manager/CHANGELOG.md |
Corrects the 3.4.6 release heading date. |
Review effort: Balanced
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
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 kind of change does this PR introduce? (Bug fix, feature, docs update...)
Docs update
The 3.4.6 CHANGELOG entry is dated 2026-10-23, the day #542 was opened, but 3.4.6 is released on 2026-10-27.
🆕 What is the new behavior (if this is a feature change)?
The entry is dated 2026-10-27, so it matches the release before
v3.4.6is tagged.💥 Does this PR introduce a breaking change?
No
🐛 Recommendations for testing
None needed; only the date in one CHANGELOG heading changes. Docs-only, so no version bump.
📝 Links to relevant issues/docs
Release step 1 in
AGENTS.md; follows #542.🤔 Checklist before submitting
🤖 Generated with Claude Code