Closed CedarMist closed 2 months ago
Name | Link |
---|---|
Latest commit | 6ea04d7d26fbcf30e9fb8c7c306db2ad15f6c352 |
Latest deploy log | https://app.netlify.com/sites/oasisprotocol-sapphire-paratime/deploys/66e6094c994b0a00087665c8 |
So quick point of thought, currently sapphire-hardhat
is 2.22.2-next.0
If I do pnpm upgrade
and v2.22.2
is in the next
dist-tag, this will upgrade to that version, but if -next
is used as a semver tag it won't.
So, I think we should keep sapphire-hardhat semver tag as next
, and release on dist-tag next
.
If I do
pnpm upgrade
andv2.22.2
is in thenext
dist-tag, this will upgrade to that version, but if-next
is used as a semver tag it won't.
Isn't this the desired behavior? 🤔
So, I think we should keep sapphire-hardhat semver tag as
next
, and release on dist-tagnext
.
Just checking, you are suggesting we keep it on -next
?
Release checklist:
clients/js/v2.0.0-next
to release @oasisprotocol/sapphire-paratime
on next
channel
git tag clients/js/v2.0.0-next
git push origin clients/js/v2.0.0-next
next
channel
npm deprecate '@oasisprotocol/sapphire-paratime@2.0.0-alpha.0' "Please use @oasisprotocol/sapphire-paratime@next"
npm deprecate '@oasisprotocol/sapphire-paratime@2.0.0-next.3' "Please use @oasisprotocol/sapphire-paratime@next"
npm dist-tag add '@oasisprotocol/sapphire-paratime@1.3.2' 'latest'
integrations/viem-v2/v2.0.1
to release @oasisprotocol/sapphire-viem-v2
on latest
channel
git tag integrations/viem-v2/v2.0.1
git push origin integrations/viem-v2/v2.0.1
latest
channelnpm deprecate '@oasisprotocol/sapphire-viem-v2@2.0.0-next.1' "Please use @oasisprotocol/sapphire-viem-v2 (without -next.1)"
npm deprecate '@oasisprotocol/sapphire-viem-v2@2.0.0-alpha.0' "Please use @oasisprotocol/sapphire-viem-v2 (without -alpha.0)"
integrations/wagmi-v2/v2.0.0
to release @oasisprotocol/sapphire-wagmi-v2
on latest
channelgit tag integrations/wagmi-v2/v2.0.0
git push origin integrations/wagmi-v2/v2.0.0
@oasisprotocol/sapphire-wagmi-v2
2.0.0-next.1
npm deprecate '@oasisprotocol/sapphire-wagmi-v2@2.0.0-next.1' "Please use @oasisprotocol/sapphire-wagmi-v2 (without -next.1)"
integrations/ethers-v6/v6.0.0
to release @oasisprotocol/sapphire-ethers-v6
on latest
channelgit tag integrations/ethers-v6/v6.0.0
git push origin integrations/ethers-v6/v6.0.0
latest
channelnpm deprecate '@oasisprotocol/sapphire-ethers-v6@6.0.0-next.1' "Please use @oasisprotocol/sapphire-ethers-v6 (without -next.1)"
npm deprecate '@oasisprotocol/sapphire-ethers-v6@6.0.0-alpha.0' "Please use @oasisprotocol/sapphire-ethers-v6 (without -alpha.0)"
integrations/hardhat/v2.22.2-next
to release @oasisprotocol/sapphire-hardhat
on next
channel, depending on @oasisprotocol/sapphire-paratime
without the semver tag.git tag integrations/hardhat/v2.22.2-next
git push origin integrations/hardhat/v2.22.2-next
Have skipped these as unnecessary
@oasisprotocol/sapphire-hardhat/2.22.2-next.0
npm deprecate '@oasisprotocol/sapphire-hardhat@2.22.2-next.0' "Please use @oasisprotocol/sapphire-hardhat (without -next.0)"
So, need to re-release packages to get versioning working correctly.
So, we're going to archive:
@oasisprotocol/sapphire-paratime
v2.0.0-alpha.0 on thelatest
tag@oasisprotocol/sapphire-paratime
v2.0.0-next.3 on thenext
tagThen release
@oasisprotocol/sapphire-paratime
v2.0.0 on thenext
tagThe
sapphire-viem-v2
,sapphire-ethers-v6
,sapphire-hardhat
andsapphire-wagmi-v2
packages will be published on their ownlatest
tags.Meaning people who
npm install @oasisprotocol/sapphire-paratime
will get v1.x by default, but if you install@oasisprotocol/sapphire-ethers-v6
you'll get@oasisprotocol/sapphire-paratime
v2 as a dependency.This means we'll be tagging
clients/js/v2.0.0-next
(to publish to thenext
dist-tag on NPMJS), butintegrations/ethers-v6/v6.0.0
(to publish tolatest
).Version resolution for dependencies on package.json will ignore the dist-tags, but adhere to any semver rules.