Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): bump go.sia.tech/coreutils from 0.3.3-0.20240927170025-f45eedc64d6f to 0.9.1 #659

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 13, 2025

Bumps go.sia.tech/coreutils from 0.3.3-0.20240927170025-f45eedc64d6f to 0.9.1.

Release notes

Sourced from go.sia.tech/coreutils's releases.

0.9.1 (2025-01-12)

Fixes

  • Release locked host UTXOs if contract formation, renewal, or refresh fails
  • Release locked UTXOs if contract formation, renewal, or refresh fails

0.9.0 (2024-12-19)

Breaking Changes

Finalize V2 Hardfork Dates

The V2 hardfork is scheduled to modernize Sia's consensus protocol, which has been untouched since Sia's mainnet launch back in 2014, and improve accessibility of the storage network. To ensure a smooth transition from V1, it will be executed in two phases. Additional documentation on upgrading will be released in the near future.

V2 Highlights

  • Drastically reduces blockchain size on disk
  • Improves UTXO spend policies - including HTLC support for Atomic Swaps
  • More efficient contract renewals - reducing lock up requirements for hosts and renters
  • Improved transfer speeds - enables hot storage

Phase 1 - Allow Height

  • Activation Height: 513400 (March 10th, 2025)
  • New Features: V2 transactions, contracts, and RHP4
  • V1 Support: Both V1 and V2 will be supported during this phase
  • Purpose: This period gives time for integrators to transition from V1 to V2
  • Requirements: Users will need to update to support the hardfork before this block height

Phase 2 - Require Height

  • Activation Height: 526000 (June 6th, 2025)
  • New Features: The consensus database can be trimmed to only store the Merkle proofs
  • V1 Support: V1 will be disabled, including RHP2 and RHP3. Only V2 transactions will be accepted
  • Requirements: Developers will need to update their apps to support V2 transactions and RHP4 before this block height

Fixes

  • Fix rhp4 server not returning ErrNotEnoughFunds when account has insufficient balance

0.8.0 (2024-12-13)

Breaking Changes

Add revised and renewed fields to RPCLatestRevision

Adds two additional fields to the RPCLatestRevision response. The Revisable field indicates whether the host will accept further revisions to the contract. A host will not accept revisions too close to the proof window or revisions on contracts that have already been resolved. The Renewed field indicates whether the contract was renewed. If the contract was renewed, the renter can use FileContractID.V2RenewalID to get the ID of the new contract.

  • Remove unused duration param from rhp4.RPCWrite

Features

Add support for block pruning in v2

The chain manager can now automatically delete blocks after a configurable number of confirmations. Note that this does not apply retroactively.

... (truncated)

Changelog

Sourced from go.sia.tech/coreutils's changelog.

0.9.1 (2025-01-12)

Fixes

  • Release locked host UTXOs if contract formation, renewal, or refresh fails
  • Release locked UTXOs if contract formation, renewal, or refresh fails

0.9.0 (2024-12-19)

Breaking Changes

Finalize V2 Hardfork Dates

The V2 hardfork is scheduled to modernize Sia's consensus protocol, which has been untouched since Sia's mainnet launch back in 2014, and improve accessibility of the storage network. To ensure a smooth transition from V1, it will be executed in two phases. Additional documentation on upgrading will be released in the near future.

V2 Highlights

  • Drastically reduces blockchain size on disk
  • Improves UTXO spend policies - including HTLC support for Atomic Swaps
  • More efficient contract renewals - reducing lock up requirements for hosts and renters
  • Improved transfer speeds - enables hot storage

Phase 1 - Allow Height

  • Activation Height: 513400 (March 10th, 2025)
  • New Features: V2 transactions, contracts, and RHP4
  • V1 Support: Both V1 and V2 will be supported during this phase
  • Purpose: This period gives time for integrators to transition from V1 to V2
  • Requirements: Users will need to update to support the hardfork before this block height

Phase 2 - Require Height

  • Activation Height: 526000 (June 6th, 2025)
  • New Features: The consensus database can be trimmed to only store the Merkle proofs
  • V1 Support: V1 will be disabled, including RHP2 and RHP3. Only V2 transactions will be accepted
  • Requirements: Developers will need to update their apps to support V2 transactions and RHP4 before this block height

Fixes

  • Fix rhp4 server not returning ErrNotEnoughFunds when account has insufficient balance

0.8.0 (2024-12-13)

Breaking Changes

Add revised and renewed fields to RPCLatestRevision

Adds two additional fields to the RPCLatestRevision response. The Revisable field indicates whether the host will accept further revisions to the contract. A host will not accept revisions too close to the proof window or revisions on contracts that have already been resolved. The Renewed field indicates whether the contract was renewed. If the contract was renewed, the renter can use FileContractID.V2RenewalID to get the ID of the new contract.

  • Remove unused duration param from rhp4.RPCWrite

Features

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [go.sia.tech/coreutils](https://github.com/SiaFoundation/coreutils) from 0.3.3-0.20240927170025-f45eedc64d6f to 0.9.1.
- [Release notes](https://github.com/SiaFoundation/coreutils/releases)
- [Changelog](https://github.com/SiaFoundation/coreutils/blob/master/CHANGELOG.md)
- [Commits](https://github.com/SiaFoundation/coreutils/commits/v0.9.1)

---
updated-dependencies:
- dependency-name: go.sia.tech/coreutils
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Jan 13, 2025
Copy link

changeset-bot bot commented Jan 13, 2025

⚠️ No Changeset found

Latest commit: ab93171

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 20, 2025

Superseded by #665.

@dependabot dependabot bot closed this Jan 20, 2025
@dependabot dependabot bot deleted the dependabot/go_modules/go.sia.tech/coreutils-0.9.1 branch January 20, 2025 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants