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

[DSHARE-1350] Add check for beacon implementation version #413

Conversation

joshualyguessennd
Copy link
Contributor

Ticket

Please link any clickup tickets, docs or other relevant context.

Description

Check implementation version before upgrading

Tests

What tests scenarios did you perform? Provide relevant screenshot/recordings here.

@joshualyguessennd joshualyguessennd requested a review from ykim as a code owner March 12, 2025 05:28
Copy link

codecov bot commented Mar 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.17%. Comparing base (70706a2) to head (ce521e2).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #413   +/-   ##
=======================================
  Coverage   89.17%   89.17%           
=======================================
  Files          15       15           
  Lines         628      628           
  Branches       73       73           
=======================================
  Hits          560      560           
  Misses         68       68           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

address beaconAddress,
address owner,
string memory currentVersion
) internal returns (address) {
address implementation = _deployImplementation(contractName);
Copy link
Contributor

Choose a reason for hiding this comment

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

This shouldn't be happening at the start of this function because it should only happen if the beacon requires an upgrade or a new deployment.

@joshualyguessennd joshualyguessennd requested a review from ykim March 12, 2025 06:51
@joshualyguessennd joshualyguessennd merged commit 5818edd into main Mar 12, 2025
9 checks passed
@joshualyguessennd joshualyguessennd deleted the DSHARE-1350-fix-beacon-deployment-previous-version-check branch March 12, 2025 06:55
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.

2 participants