chore(release): bump to 0.30.4 - #498
Merged
Merged
Conversation
Patch release: one behavioural fix (removal of the dead CodelessDebugLogEnabled manifest entry) plus documentation changes. No API surface change. pubspec.yaml and ios/facebook_app_events.podspec are kept in sync per CONTRIBUTING.md. The CHANGELOG's "Unreleased" heading becomes "## 0.30.4" because build_deploy.yml extracts release notes by matching a literal "## <version>" heading and fails the release job if it finds none. Graph API pin left at v24.0. The release-time check now recorded in CONTRIBUTING.md does flag that the current latest is v26.0, but bumping the pin is a behavioural change that deserves its own PR rather than riding along in a release commit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Prepares the facebook_app_events Flutter plugin for the 0.30.4 release by updating the package version metadata and promoting the changelog entry from “Unreleased” to a versioned heading, aligning with the documented release process and the release-notes extraction workflow.
Changes:
- Bumped the Dart package version to
0.30.4inpubspec.yaml. - Kept the CocoaPods spec version in sync by bumping
ios/facebook_app_events.podspecto0.30.4. - Renamed the top
CHANGELOG.mdheading from## Unreleasedto## 0.30.4to support automated release-notes extraction.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| pubspec.yaml | Updates the package version to 0.30.4 for pub.dev publishing. |
| ios/facebook_app_events.podspec | Keeps the CocoaPods spec version aligned with the Dart package version (0.30.4). |
| CHANGELOG.md | Promotes the pending release notes to a versioned ## 0.30.4 heading for the release workflow. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Release prep for 0.30.4, following the
CONTRIBUTING.mdrelease process.What changed
pubspec.yaml→0.30.4ios/facebook_app_events.podspec→0.30.4(kept in sync, otherwise CocoaPods consumers resolve the wrong version)CHANGELOG.md:## Unreleased→## 0.30.4Why the heading rename matters
build_deploy.ymlbuilds release notes withawkmatching a literal## <version>heading andexit 1s if it finds none. An## Unreleasedheading would have failed the release job after publishing had already happened.Version choice
Patch. The release contains one behavioural fix (removing the dead
CodelessDebugLogEnabledmanifest entry) and documentation changes. No API surface change, nothing breaking.Pre-flight
flutter analyzecleanflutter pub publish --dry-runclean apart from the uncommitted-files warning (now committed)awkexpressionpubspec.yamland podspec versions matchGraph API pin: check fired, deliberately not acted on
The release-time check added in the previous PR does its job on first use: the pin is
v24.0, the current latest isv26.0. Not bumped here. That is a behavioural change and belongs in its own PR with its own review, not folded into a release commit.Heads up on what merging leads to
Pushing the
v0.30.4tag triggersbuild_deploy.yml, which runsflutter pub publish --forceand then cuts a GitHub Release. That publish is irreversible (pub.dev versions can be retracted but never deleted). I will not push the tag without you confirming.Separately:
docs/is currently untracked and not gitignored.pub publishincludes untracked-but-unignored files, so committing it would shipWEBSITE-HANDOFF.md(revenue figures, pricing, click baselines) to pub.dev. CI publishes from a clean checkout so today's archive is unaffected.🤖 Generated with Claude Code