Require PR approval before release tagging#1693
Merged
Merged
Conversation
This version includes a `validate_pr_approved` check in `tag-current-branch` that verifies the release PR has been approved before the tag is created. Made-with: Cursor
7903031 to
b7a623a
Compare
tonidero
approved these changes
Mar 23, 2026
RCGitBot
added a commit
that referenced
this pull request
Apr 1, 2026
**This is an automatic release.** ## RevenueCat SDK ### ✨ New Features * Lower minimum Flutter SDK to 3.22.0 and Dart to 3.4.0 (#1704) via Rick (@rickvdl) ### 📦 Dependency Updates * [AUTOMATIC BUMP] Updates purchases-hybrid-common to 17.54.0 (#1703) via RevenueCat Git Bot (@RCGitBot) * [Android 9.28.1](https://github.com/RevenueCat/purchases-android/releases/tag/9.28.1) * [Android 9.28.0](https://github.com/RevenueCat/purchases-android/releases/tag/9.28.0) * [iOS 5.67.0](https://github.com/RevenueCat/purchases-ios/releases/tag/5.67.0) ### 🔄 Other Changes * Bump fastlane-plugin-revenuecat_internal from `9a6911b` to `f11fe40` (#1701) via dependabot[bot] (@dependabot[bot]) * security: pin GitHub Actions to SHA hashes (#1697) via Alfonso Embid-Desmet (@alfondotnet) * Bump activesupport from 7.2.3 to 7.2.3.1 (#1696) via dependabot[bot] (@dependabot[bot]) * Merge release PR after deploy (#1694) via Antonio Pallares (@ajpallares) * Require PR approval before release tagging (#1693) via Antonio Pallares (@ajpallares) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Primarily a coordinated version/release bump across Flutter, Android, iOS/macOS, and web with updated dependency versions and minimum SDK constraints; no functional logic changes beyond version metadata. > > **Overview** > Bumps the Flutter SDK release from `9.15.1` to `9.16.0` across package metadata (`.version`, `pubspec.yaml`, podspecs, Gradle files) and updates the embedded plugin version constants for Android/iOS/web. > > Updates release documentation (`CHANGELOG-LATEST.md`, `CHANGELOG.md`, `VERSIONS.md`) to include the `9.16.0` notes, including the lowered minimum Flutter/Dart requirements and the `purchases-hybrid-common` bump to `17.54.0` (with corresponding native iOS/Android version references). Also updates `purchases_ui_flutter` to depend on `purchases_flutter ^9.16.0`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit c93cfb2. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
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.
Motivation
The release workflow currently allows tagging a release branch without verifying that the PR has been reviewed and approved. This adds a safeguard to ensure the release PR is properly approved before the tag is created.
Description
Bumps
revenuecat/sdks-common-configorb to@3.16.0, which includes avalidate_pr_approvedstep in thetag-current-branchjob. This verifies the release PR has been approved by an org member with write permissions before the git tag is created.Depends on: RevenueCat/sdks-circleci-orb#41
Note
Medium Risk
Changes the release/tagging workflow behavior via an orb upgrade, which could block or alter release tagging if the new PR-approval validation misbehaves or is misconfigured.
Overview
Updates the CircleCI
revenuecat/sdks-common-configorb from3.13.0to3.16.0, pulling in new behavior for therevenuecat/tag-current-branchjob (including PR-approval validation) before creating release tags.Written by Cursor Bugbot for commit 604173c. This will update automatically on new commits. Configure here.