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

Begin codifying the use of NPM dist-tags #4117

Merged
merged 4 commits into from
Nov 24, 2021
Merged

Begin codifying the use of NPM dist-tags #4117

merged 4 commits into from
Nov 24, 2021

Conversation

michaelfig
Copy link
Member

@michaelfig michaelfig commented Nov 24, 2021

refs: #3857

Description

Begin distinguishing between latest, dev (and hopefully soon beta) tags that users can agoric install latest in order to keep their dapp dependencies up-to-date.

This will make dapp dependency management more like typical Yarn. We also add a CI dev-canary publish on push to master, so that agoric install dev will get the freshest code.

Drive-by: try incorporating the Node 16 CXXFLAGS support discovered by @robert-zaremba.

Security Considerations

Documentation Considerations

Testing Considerations

@michaelfig michaelfig added agoric-cli package: agoric-cli tooling repo-wide infrastructure labels Nov 24, 2021
@michaelfig michaelfig self-assigned this Nov 24, 2021
Copy link
Member

@dckc dckc left a comment

Choose a reason for hiding this comment

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

I have a few questions. Nothing critical.

Our release notes still suffer quite a bit from lax use of conventional commits, i.e. not writing each commit message consciously as a contribution to the release notes.

/******/ ]);
Copy link
Member

Choose a reason for hiding this comment

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

TIL: we keep copies of yarn releases in our tree


* **ERTP:** NatValues now only accept bigints, lower-case amountMath is removed, and AmountMath methods always follow the order of: brand, value

* chore: fix up INPUT_VALIDATON.md
Copy link
Member

Choose a reason for hiding this comment

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

Odd looking breaking change


### ⚠ BREAKING CHANGES

* remove newSwap; replace with constantProduct AMM where needed (#4097)
Copy link
Member

Choose a reason for hiding this comment

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

In the swingset package, removing newswap doesn't seem like a breaking change. I bet it's just some test reorg that ideally would have been a separate commit. I suppose I reviewed this one but didn't consider how squashing would impact release notes

@@ -57,5 +57,8 @@
"test/**/test-*.js"
],
"timeout": "2m"
},
"publishConfig": {
"access": "public"
Copy link
Member

Choose a reason for hiding this comment

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

Commit message seems like it could be more specific

CHANGELOG.md Outdated Show resolved Hide resolved
packages/deployment/package.json Outdated Show resolved Hide resolved
@michaelfig michaelfig force-pushed the mfig-npm-dev branch 8 times, most recently from c2aea65 to 3838b3e Compare November 24, 2021 18:02
Also, pivot to `latest` NPM dist-tag.
@michaelfig michaelfig force-pushed the mfig-npm-dev branch 3 times, most recently from e6dfb2a to 9ba832e Compare November 24, 2021 19:21
# Adapted from https://johnny.sh/notes/publish-canary-lerna-cicd/
- name: configure NPM token
run: |
echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" > ~/.npmrc
Copy link
Member

Choose a reason for hiding this comment

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

NPM_TOKEN looks like a very pointy instrument: it seems to represent authority to update all our packages in npm.

I'd like to get @warner 's take on this.

Copy link
Member Author

Choose a reason for hiding this comment

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

Please move this discussion to #4120.

@dckc dckc self-requested a review November 24, 2021 19:44
@dckc
Copy link
Member

dckc commented Nov 24, 2021

looks like this refs: #3857

@michaelfig michaelfig force-pushed the mfig-npm-dev branch 2 times, most recently from 4532ba9 to 6ee4e6e Compare November 24, 2021 21:40
@michaelfig michaelfig added the automerge:no-update (expert!) Automatically merge without updates label Nov 24, 2021
@mergify mergify bot merged commit 98d414a into master Nov 24, 2021
@mergify mergify bot deleted the mfig-npm-dev branch November 24, 2021 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agoric-cli package: agoric-cli automerge:no-update (expert!) Automatically merge without updates tooling repo-wide infrastructure
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants