Merge pull request #5798 from stacks-network/release/3.1.0.0.5

Merge 3.1.0.0.5 to develop

Author: kantai

CHANGELOG.md

@@ -9,6 +9,14 @@ and this project adheres to the versioning scheme outlined in the [README.md](RE
 
 ### Added
 
+### Changed
+
+### Fixed
+
+## [3.1.0.0.5]
+
+### Added
+
 - Add miner configuration option `tenure_extend_cost_threshold` to specify the percentage of the tenure budget that must be spent before a time-based tenure extend is attempted
 
 ### Changed

stacks-signer/CHANGELOG.md

@@ -9,6 +9,12 @@ and this project adheres to the versioning scheme outlined in the [README.md](RE
 
 ### Added
 
+### Changed
+
+## [3.1.0.0.5.0]
+
+### Added
+
 - Add `dry_run` configuration option to `stacks-signer` config toml. Dry run mode will
   run the signer binary as if it were a registered signer. Instead of broadcasting
   `StackerDB` messages, it logs `INFO` messages. Other interactions with the `stacks-node`
@@ -17,44 +23,44 @@ and this project adheres to the versioning scheme outlined in the [README.md](RE
 
 ## [3.1.0.0.4.0]
 
-## Added
+### Added
 
 - When a new block proposal is received while the signer is waiting for an existing proposal to be validated, the signer will wait until the existing block is done validating before submitting the new one for validating. ([#5453](https://github.com/stacks-network/stacks-core/pull/5453))
 - Introduced two new prometheus metrics:
   - `stacks_signer_block_validation_latencies_histogram`: the validation_time_ms reported by the node when validating a block proposal
   - `stacks_signer_block_response_latencies_histogram`: the "end-to-end" time it takes for the signer to issue a block response
 
-## Changed
+### Changed
 
 ## [3.1.0.0.3.0]
 
-## Added
+### Added
 
 - Introduced the `block_proposal_max_age_secs` configuration option for signers, enabling them to automatically ignore block proposals that exceed the specified age in seconds.
 
-## Changed
+### Changed
 - Improvements to the stale signer cleanup logic: deletes the prior signer if it has no remaining unprocessed blocks in its database
 - Signers now listen to new block events from the stacks node to determine whether a block has been successfully appended to the chain tip
 
-# [3.1.0.0.2.1]
+## [3.1.0.0.2.1]
 
-## Added
+### Added
 
-## Changed
+### Changed
 
 - Prevent old reward cycle signers from processing block validation response messages that do not apply to blocks from their cycle.
 
-# [3.1.0.0.2.1]
+## [3.1.0.0.2.1]
 
-## Added
+### Added
 
-## Changed
+### Changed
 
 - Prevent old reward cycle signers from processing block validation response messages that do not apply to blocks from their cycle.
 
 ## [3.1.0.0.2.0]
 
-## Added
+### Added
 
 - **SIP-029 consensus rules, activating in epoch 3.1 at block 875,000** (see [SIP-029](https://github.com/will-corcoran/sips/blob/feat/sip-029-halving-alignment/sips/sip-029/sip-029-halving-alignment.md) for details)