Skip to content

feat: simplified release process#7409

Merged
brice-stacks merged 729 commits into
stacks-network:release/4.0.0from
brice-stacks:release/4.0.0-updates
Jul 10, 2026
Merged

feat: simplified release process#7409
brice-stacks merged 729 commits into
stacks-network:release/4.0.0from
brice-stacks:release/4.0.0-updates

Conversation

@brice-stacks

Copy link
Copy Markdown
Contributor
  • Just MAJOR.MINOR.PATCH in version number
  • Just one release, no separate signer release

This is intended to merge into a release/4.0.0 which is reset to the latest develop, commit b3823f10cc4f1982c740741ee86e17f5136254c6, with the pox-wf-integration branch merged in. Just the last two commits are new.

radu-stacks and others added 30 commits June 9, 2026 19:38
…-reserve-fn

feat: add private function for spending pox-5 reserve
…ithdrawals

feat: handle failed sBTC withdrawals and sweeping excess fees
…1-info

feat: update print info in register-for-bond
This cannot be called indirectly, so we should use `contract-caller`
instead of `tx-sender`.
…igner-grant

fix: require `revoke-signer-grant` to be called directly
Removed the `allow-contract-caller`, `disallow-contract-caller`, and
`check-caller-allowed` functions and the `allowance-contract-callers`
map from `pox-5`. Stacking methods may now be invoked through any
contract-caller; stackers protect themselves with the in-contract
`with-stacking` / `with-pox` allowances or transaction-level `Staking`
/ `Pox` post-conditions instead.

Added transaction-level `Staking` and `Pox` post-conditions, and
matching in-contract `with-staking` / `with-pox` allowances. `Staking`
constrains how much STX a principal may stake (lock for PoX) during a
transaction. `Pox` gates the state-altering PoX-5 operations that act
on a principal's existing position: `unstake`, `unstake-sbtc`,
`update-bond-registration`, and `announce-l1-early-exit`, and is
presence-based (block / allow / require). Both are only valid in Stacks
epoch 4.0 and later, and in `Deny`/`Originator` post-condition mode an
uncovered stake or PoX action fails the transaction. In Clarity 6 the
`with-stacking` allowance was renamed to `with-staking` (the old
`with-stacking` spelling remains valid in Clarity 4 and 5).
aaronb-stacks and others added 8 commits July 9, 2026 11:56
…ty-commit

Fix: handle 0-sat bitcoin output edge-case
…acks-epoch-id-range-ops-for-testing

testing: epoch range support for test builds and minor refactors to use them
…-to-pox-wf-conflicts

Merge `develop` into `pox-wf-integration`
- Just MAJOR.MINOR.PATCH in version number
- Just one release, no separate signer release

@cylewitruk-stacks cylewitruk-stacks left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm; had Copilot perform a three-way comparison between pox-wf-integration, develop and this branch and it confirmed everything lined up with only release versioning/scaffolding/CI changes here.

hstove-stacks
hstove-stacks previously approved these changes Jul 10, 2026
@brice-stacks

Copy link
Copy Markdown
Contributor Author

Taking a look at the nix error...

Comment thread .github/actions/release/create-github-release/release.template
Comment thread .github/scripts/draft_release.sh
dhaney-stacks
dhaney-stacks previously approved these changes Jul 10, 2026

@dhaney-stacks dhaney-stacks left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, unfortunately mostly a thing we can only test "live" (note to self: a manual "dry run" flag might be great in the future for release testing). We can remediate issues mid-flight if any are encountered during 4.0.0 release.

@brice-stacks
brice-stacks merged commit 384d995 into stacks-network:release/4.0.0 Jul 10, 2026
236 of 238 checks passed
@brice-stacks
brice-stacks deleted the release/4.0.0-updates branch July 10, 2026 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants