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

Update dependency @unlock-protocol/contracts to ^0.0.33 #2

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 10, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@unlock-protocol/contracts (source) ^0.0.15 -> ^0.0.33 age adoption passing confidence

Release Notes

unlock-protocol/unlock (@​unlock-protocol/contracts)

v0.0.33

Compare Source

v0.0.32

Compare Source

v0.0.31

Compare Source

  • Add PublicLock v15 and Unlock v14

Features

  • remember referrer for renewals (#​15017) - the referrer address set during the first purchase is now automatically reused when a key is renewed (for subscriptions)
  • burn / disable a lock entirely (#​15018) - “burning” a lock will disbale all features and make existing data inaccessible. To date, this can NOT be reversed (even though nothing is deleted from chain storage).
  • Purchase multiple periods at once (#​14845) - one can chose to buy directly several periods for a key during a single purchase
  • update reward computation to be based on protocol fee (#​14696) - the gov tokens reward is now based on a fraction of the protocol fee - more precisely: the amount of governance tokens distributed is equal to half the protocol fee
  • add hasRole hook (#​14829) - a new hook can be used to set programmatically a role based on a 3rd part custom contract
  • dissociate referrer from protocolReferrer (#​15042) - allow to specify different addresses to perceive referrer fees and governance token reward

Minor / internal changes

  • adding the ability to execute more tx as part of a deployment. (#​14877) - some actions can now be added directly to the transaction where a lock is created (for instance, set another lock manager, etc).
  • use struct to parse purchase args (#​14806) - we use a new signature to parse purchase arguments, more flexible and clearer
  • emit PaymentReceipt event (#​14832)
  • add ReferrerPaid event (#​14827)
  • replace udt by governanceToken in Unlock contract (#​14688) (udt has been kept for backwards compatibility reasons)

Fixes

  • owners count excludes the zero address (#​14828)
  • lower contract size for PublicLock v15 (#​14846) removes addLockManager shorthand
  • wrong token id after a key was burnt (#​15071)

v0.0.30

Compare Source

  • Remove deprecated versions of Unlock (from V0 to v10)
  • Remove deprecated versions of PublicLock (from V0 to v7)

v0.0.29

Compare Source

  • Adding EmptyImpl in utils to allow deploymeny of empty proxy
  • Update UPToken and UPSwap initialization logic

v0.0.27

Compare Source

  • add UPToken, UPGovernor, UPTimelock and UPSwap contracts

v0.0.26

Compare Source

  • update UniswapOracleV3 to allow pool fee to be passed in constructor

v0.0.25

Compare Source

  • update UnlockSwapBurner to latest version using Uniswap UniversalRouter

v0.0.24

Compare Source

  • add contracts alias for all versions
  • add PublicLock and Unlock alias for all versions
  • add version numbers as constant

v0.0.23

Compare Source

v0.0.22

Compare Source

  • add contracts alias for all versions
  • add PublicLock and Unlock alias for all versions
  • add version numbers as constant

v0.0.21

Compare Source

  • release fix post-attack on Fri Apr 21st 2023 #​11690

v0.0.20

Compare Source

  • release storage slot fix for PublicLock V13 #​11665

v0.0.19

Compare Source

  • improve docstrings and fix some typo in IUnlock and IPublicLock interfaces

v0.0.18

Compare Source

  • PublicLockV13: update hardcoded Unlock mainnet address with redeployed version

v0.0.16

Compare Source

  • added PublicLock v13 and Unlock v12

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/unlock-protocol-contracts-0.x branch from e73480f to 20c51b1 Compare May 29, 2023 15:57
@renovate renovate bot changed the title Update dependency @unlock-protocol/contracts to ^0.0.16 Update dependency @unlock-protocol/contracts to ^0.0.22 May 29, 2023
@renovate renovate bot force-pushed the renovate/unlock-protocol-contracts-0.x branch from 20c51b1 to 05f9815 Compare March 15, 2024 12:00
@renovate renovate bot changed the title Update dependency @unlock-protocol/contracts to ^0.0.22 Update dependency @unlock-protocol/contracts to ^0.0.23 Mar 15, 2024
@renovate renovate bot force-pushed the renovate/unlock-protocol-contracts-0.x branch from 05f9815 to e7259ee Compare March 21, 2024 08:49
@renovate renovate bot changed the title Update dependency @unlock-protocol/contracts to ^0.0.23 Update dependency @unlock-protocol/contracts to ^0.0.25 Mar 21, 2024
@renovate renovate bot force-pushed the renovate/unlock-protocol-contracts-0.x branch from e7259ee to 25a0d63 Compare April 16, 2024 23:26
@renovate renovate bot changed the title Update dependency @unlock-protocol/contracts to ^0.0.25 Update dependency @unlock-protocol/contracts to ^0.0.26 Apr 16, 2024
@renovate renovate bot force-pushed the renovate/unlock-protocol-contracts-0.x branch from 25a0d63 to 50e5fcd Compare May 8, 2024 23:58
@renovate renovate bot changed the title Update dependency @unlock-protocol/contracts to ^0.0.26 Update dependency @unlock-protocol/contracts to ^0.0.27 May 8, 2024
@renovate renovate bot force-pushed the renovate/unlock-protocol-contracts-0.x branch from 50e5fcd to 3c333c9 Compare July 10, 2024 02:42
@renovate renovate bot changed the title Update dependency @unlock-protocol/contracts to ^0.0.27 Update dependency @unlock-protocol/contracts to ^0.0.29 Jul 10, 2024
@renovate renovate bot force-pushed the renovate/unlock-protocol-contracts-0.x branch from 3c333c9 to c17c167 Compare July 21, 2024 05:45
@renovate renovate bot changed the title Update dependency @unlock-protocol/contracts to ^0.0.29 Update dependency @unlock-protocol/contracts to ^0.0.30 Jul 21, 2024
@renovate renovate bot force-pushed the renovate/unlock-protocol-contracts-0.x branch from c17c167 to 5bf6b28 Compare September 10, 2024 17:57
@renovate renovate bot changed the title Update dependency @unlock-protocol/contracts to ^0.0.30 Update dependency @unlock-protocol/contracts to ^0.0.31 Sep 10, 2024
@renovate renovate bot force-pushed the renovate/unlock-protocol-contracts-0.x branch from 5bf6b28 to f168205 Compare November 27, 2024 17:52
@renovate renovate bot changed the title Update dependency @unlock-protocol/contracts to ^0.0.31 Update dependency @unlock-protocol/contracts to ^0.0.32 Nov 27, 2024
@renovate renovate bot force-pushed the renovate/unlock-protocol-contracts-0.x branch from f168205 to eef9d9a Compare December 14, 2024 02:41
@renovate renovate bot changed the title Update dependency @unlock-protocol/contracts to ^0.0.32 Update dependency @unlock-protocol/contracts to ^0.0.33 Dec 14, 2024
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.

0 participants