Skip to content

Conversation

@mujahidkay
Copy link
Member

@mujahidkay mujahidkay commented Nov 6, 2025

adopt a passed proposal

When a proposal passes on agoric-3 Mainnet, it should be included in the history that this synthetic image tracks.

  • before this PR, change any fromTag using latest (such as a3p-integration) to use a fixed version (otherwise they will fail when this PR changes latest and they pick it up)

tooling improvements

As long as it passes CI it should be fine.

@semanticdiff-com
Copy link

semanticdiff-com bot commented Nov 6, 2025

Review changes with  SemanticDiff

Changed Files
File Status
  .github/actions/setup-node/action.yml  0% smaller
  proposals/110:upgrade-22/.gitignore Unsupported file format
  proposals/110:upgrade-22/.yarnrc.yml  0% smaller
  proposals/110:upgrade-22/README.md Unsupported file format
  proposals/110:upgrade-22/package.json  0% smaller
  proposals/110:upgrade-22/test.sh Unsupported file format
  proposals/110:upgrade-22/test/initial.test.js  0% smaller
  proposals/110:upgrade-22/tsconfig.json  0% smaller
  proposals/110:upgrade-22/yarn.lock Unsupported file format

@changeset-bot
Copy link

changeset-bot bot commented Nov 6, 2025

⚠️ No Changeset found

Latest commit: 6a2b1d4

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

@mujahidkay mujahidkay self-assigned this Nov 6, 2025
@mujahidkay mujahidkay force-pushed the mk/u22 branch 2 times, most recently from 2054970 to 5840e41 Compare November 7, 2025 09:36
uses u22b tags, image and commit hashes
our tooling currently doesn't work with node 24 so downgrading to 22
@mujahidkay mujahidkay marked this pull request as ready for review November 7, 2025 11:33
@mujahidkay mujahidkay requested a review from Muneeb147 November 7, 2025 11:37
Copy link

@Muneeb147 Muneeb147 left a comment

Choose a reason for hiding this comment

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

LGTM.
Just one concern.

Comment on lines +5 to +10
"planName": "agoric-upgrade-22",
"upgradeInfo": {
"binaries": {
"any": "https://github.com/Agoric/agoric-sdk/archive/d15cbb93a8c1e96b364de7d961909ff1199876e5.zip//agoric-sdk-d15cbb93a8c1e96b364de7d961909ff1199876e5?checksum=sha256:3d1252d62cd57db86848707692f636e9518d02338eb538933238dad3b4c5b243"
},
"source": "https://github.com/Agoric/agoric-sdk/archive/d15cbb93a8c1e96b364de7d961909ff1199876e5.zip?checksum=sha256:3d1252d62cd57db86848707692f636e9518d02338eb538933238dad3b4c5b243"
Copy link

@Muneeb147 Muneeb147 Nov 7, 2025

Choose a reason for hiding this comment

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

It is technically aligning to https://github.com/Agoric/agoric-sdk/releases/tag/agoric-upgrade-22b as we're using 69 tag and relevant commit-hash, right?

So shouldn't we change releaseNotes link to https://github.com/Agoric/agoric-sdk/releases/tag/agoric-upgrade-22b?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, I'm not sure which release to put in releaseNotes. Ideally, it should be all 3 (22, 22a and 22b).

Copy link
Member Author

Choose a reason for hiding this comment

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

The actual chain software upgrade was agoric-upgrade-22, hence I opted for its release notes. But the code is indeed for u22b which includes the two patches. Shouldn't be a merge blocker though, we can always update this later on.

@mujahidkay mujahidkay merged commit f7a3684 into main Nov 7, 2025
41 checks passed
@mujahidkay mujahidkay deleted the mk/u22 branch November 7, 2025 13:11
- uses: actions/setup-node@v4
with:
node-version: lts/*
node-version: 22
Copy link
Member

Choose a reason for hiding this comment

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

What broke? We need an issue. Agoric officially supports all LTS

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