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

use particular fromTag in a3p-integration #10056

Merged
merged 4 commits into from
Sep 10, 2024
Merged

Conversation

turadg
Copy link
Member

@turadg turadg commented Sep 10, 2024

incidental

Description

Use a particular fromTag to avoid build errors when agoric-3-proposals advances latest.

Also changes the proposal id for upgrade-next from e to n to make it easier to remember, give ample namespace preceding it and make it very obvious from a proposal ID that it's after the next upgrade. E.g. s:stake-bld (which had been g:stake-bld)

Security Considerations

n/a

Scaling Considerations

n/a

Documentation Considerations

Updated docs here. Agoric/agoric-3-proposals#180 should align.

Testing Considerations

CI

Upgrade Considerations

n/a

Copy link

cloudflare-workers-and-pages bot commented Sep 10, 2024

Deploying agoric-sdk with  Cloudflare Pages  Cloudflare Pages

Latest commit: 32163ea
Status: ✅  Deploy successful!
Preview URL: https://c171fc0d.agoric-sdk.pages.dev
Branch Preview URL: https://ta-a3p-use-particular.agoric-sdk.pages.dev

View logs

Comment on lines 81 to 83
Once a new proposal is merged into agoric-3-proposals, take the proposal name
(the part after the colon) and make it the fromTag value in a3p-integration's
package.json.
Copy link
Member

Choose a reason for hiding this comment

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

make it the fromTag value

This might be a little confusing since the tag would actually be formed as use-${proposalName}

If you're changing the fromTag to a a new SDK version (e.g. a new chain-halting
upgrade) then you also need to revise the `upgrade-next` proposal to be able to
apply on top of that upgrade. In master it should already have these values,
which should be maintained:
Copy link
Member

Choose a reason for hiding this comment

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

Incidental, below there is still a reference to app.go. The relevant logic was moved to upgrade.go (I thought I caught all occurrences in #9694 to track the change from #9575)

They are lexically ordered but there are enough letters in the alphabet that we can make them easier to remember. In particular "n" for next upgrade.
@turadg turadg force-pushed the ta/a3p-use-particular branch from 6b4389a to 32163ea Compare September 10, 2024 19:06
@turadg turadg added bypass:automerge Allow manually merging a PR automerge:rebase Automatically rebase updates, then merge bypass:integration Prevent integration tests from running on PR and removed bypass:automerge Allow manually merging a PR labels Sep 10, 2024
@mergify mergify bot merged commit a9e951a into master Sep 10, 2024
104 of 105 checks passed
@mergify mergify bot deleted the ta/a3p-use-particular branch September 10, 2024 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge:rebase Automatically rebase updates, then merge bypass:integration Prevent integration tests from running on PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants