Repository navigation
🚀🧑💻 - 1.5.2 - Release recover package publication safely #170
Description
Release Type
Patch
Release Version
1.5.2
Changelog
-
Fix package publication so Flutter resolves only the distributable package, without resolving example apps that mix local and hosted dependencies.
-
Renew pub.dev OIDC credentials for each package after the previous package has finished indexing.
-
Retain all release-preparation fixes and generated artifacts accepted in production by PR release(1.5.1): promote to master #169; regenerate every distributable artifact in the new deployment preparation phase.
-
Document recovery from a partial immutable publication.
-
Minimum supported SDKs remain Dart ^3.12.0 and Flutter >=3.44.0; release validation uses Flutter 3.47.2.
-
Make release verification reproducible with job-local Flutter/Dart and native test dependencies, and isolate publication token references from ordinary CI.
Additional Context
The maintainer explicitly authorized correcting and publishing patch 1.5.2 through Copilot after reviewing the failed 1.5.1 publication.
Release issue #168 / PR #169 promoted production commit 804c1a8 under immutable tag v1.5.1. Publication run https://github.com/vypdev/zstandard/actions/runs/40293596999 published six packages (platform_interface, native, Android, iOS, Linux, macOS). Web, Windows, CLI and the main package remain at 1.5.0. The third attempt fails deterministically while resolving the Web example. Earlier attempts also exposed credential expiry; the private pub.dev environment mismatch was corrected by the maintainer.
Keep v1.5.1, its accepted source, six published package versions and historical operation unchanged. Do not claim that 1.5.1 finished publication. Preserve installed Copilot files, workflows, policy, operation receipts and lifecycle ownership.
Before freezing a 1.5.2 candidate, use Copilot's supported synchronization control to retain production/master fixes in the new managed release branch. Implement the reviewed product-publisher correction and regression tests on that Action-created branch. All external action references must use version tags (@v1, @v2, etc.), never commit SHAs.
Copilot must perform version updates, WebAssembly generation, all native library builds, validation, protected production promotion, tagging, publication and final development reconciliation through the existing deployment system. No local package uploads or manually created tags/branches.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[-]Release 1.5.2: recover package publication safely[/-][+]🚀 - 1.5.2 - Release recover package publication safely[/+][-]🚀 - 1.5.2 - Release recover package publication safely[/-][+]🚀🧑💻 - 1.5.2 - Release recover package publication safely[/+]efraespada commentedon Oct 26, 2026
/copilot sync-branch --from master --no-agent
44 remaining items
vypbot commentedon Oct 26, 2026
❌ Release
1.5.2Action required
Package publication failed. Review https://github.com/vypdev/zstandard/actions/runs/40430400481 and rerun this immutable tag workflow.. Retry after correcting the cause.
What Copilot protected
Production updated: Yes. Package status: not published.
Progress
develop@22eb4demasterdevelopflowchart LR D[Source snapshot] --> R[Version prepared] R --> P[Production PR] P --> A[Accepted in production] A --> N[Package and release] N --> B[Development reconciliation] B --> C[Complete]prepared -> production PR -> accepted -> published -> reconciled -> complete
Current transition
release/1.5.2masterLinks
Release control center · release/1.5.2 branch · 22eb4de origin commit · 7f4425b prepared commit · Compare changes · Promotion PR #174 · aca7c11 production commit
Technical details
df2ae6c3-f7df-4fe4-ae59-80a5793c4727production-lineageauto-merge7f4425b839a4b34dafc36fbf3d9d00bc2a880e07aca7c1162962d59a2c7287871c95868e34c97e0evypbot commentedon Oct 28, 2026
Issue closed: synchronization recommendation retired
No branch synchronization is required for this closed issue.
The previous recommendation is historical. Issue closure does not certify that the branches are synchronized.