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

move: pause tracking a package in config.toml #16032

Merged
merged 1 commit into from
Jan 31, 2024
Merged

Conversation

rvantonder
Copy link
Contributor

Description

The source for this package is moving on the master branch kunalabs-io/sui-smart-contracts@e6fcbd6 which shouldn't happen when we're tracking it for bytecode verification. When it moves, but the published address stays the same, the bytecode no longer matches upstream and the service pauses.

I'll get in touch with package maintainers to figure out how we can pin the source to a branch that doesn't move or is being actively developed against, and will then re-enable.

Test Plan

N/A, maintaining source service.


If your changes are not user-facing and do not break anything, you can skip the following section. Otherwise, please briefly describe what has changed under the Release Notes section.

Type of Change (Check all that apply)

  • protocol change
  • user-visible impact
  • breaking change for a client SDKs
  • breaking change for FNs (FN binary must upgrade)
  • breaking change for validators or node operators (must upgrade binaries)
  • breaking change for on-chain data layout
  • necessitate either a data wipe or data migration

Release notes

@rvantonder rvantonder requested review from a team January 31, 2024 22:22
Copy link

vercel bot commented Jan 31, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
mysten-ui ✅ Ready (Inspect) Visit Preview Jan 31, 2024 10:22pm
sui-typescript-docs ✅ Ready (Inspect) Visit Preview Jan 31, 2024 10:22pm
3 Ignored Deployments
Name Status Preview Updated (UTC)
explorer ⬜️ Ignored (Inspect) Jan 31, 2024 10:22pm
multisig-toolkit ⬜️ Ignored (Inspect) Jan 31, 2024 10:22pm
sui-kiosk ⬜️ Ignored (Inspect) Jan 31, 2024 10:22pm

@rvantonder rvantonder enabled auto-merge (squash) January 31, 2024 22:26
@rvantonder rvantonder merged commit 4acefbd into main Jan 31, 2024
41 checks passed
@rvantonder rvantonder deleted the rvt/pause-package branch January 31, 2024 22:40
rvantonder added a commit that referenced this pull request Feb 13, 2024
## Description 

As in title. The config now supports specifying multiple branches per
repository:

```toml
[[packages.values.branches]]
branch = "framework/mainnet"
paths = [
  { path = "crates/sui-framework/packages/deepbook", watch = "0xdee9" },
  { path = "crates/sui-framework/packages/move-stdlib", watch = "0x1" },
  { path = "crates/sui-framework/packages/sui-framework", watch = "0x2" },
  { path = "crates/sui-framework/packages/sui-system", watch = "0x3" }
]
[[packages.values.branches]]
# ... more ...
```

Useful for supporting external packages, with this we can now
effectively version sources that implement a bespoke branch naming
scheme for immutable packages (`mainnet-v0`, `mainnet-v1`, etc.) Related
to better supporting external packages, see
#16032

## Test Plan 

Updated existing tests to exercise changes (clone commands, finding
branch clone destination)

---
If your changes are not user-facing and do not break anything, you can
skip the following section. Otherwise, please briefly describe what has
changed under the Release Notes section.

### Type of Change (Check all that apply)

- [ ] protocol change
- [ ] user-visible impact
- [ ] breaking change for a client SDKs
- [ ] breaking change for FNs (FN binary must upgrade)
- [ ] breaking change for validators or node operators (must upgrade
binaries)
- [ ] breaking change for on-chain data layout
- [ ] necessitate either a data wipe or data migration

### Release notes
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.

4 participants