-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
feat: contracts publishing in CI #12102
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I see that you haven't updated any CHANGELOG files. Would it make sense to do so? |
erikburt
force-pushed
the
test/npm-contracts-publishing
branch
from
February 27, 2024 04:51
9a60a20
to
892fc71
Compare
erikburt
changed the title
[WIP] feat: contracts publishing in CI
feat: contracts publishing in CI
Feb 27, 2024
erikburt
force-pushed
the
test/npm-contracts-publishing
branch
from
February 28, 2024 22:21
05020e0
to
a1b67ec
Compare
momentmaker
reviewed
Feb 28, 2024
momentmaker
reviewed
Feb 28, 2024
momentmaker
reviewed
Feb 28, 2024
momentmaker
reviewed
Feb 28, 2024
momentmaker
previously approved these changes
Feb 29, 2024
chainchad
previously approved these changes
Feb 29, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! One small comment though to confirm.
erikburt
commented
Apr 3, 2024
chainchad
previously approved these changes
Apr 3, 2024
chainchad
approved these changes
Apr 4, 2024
CL-Andrew
approved these changes
Apr 4, 2024
Quality Gate passedIssues Measures |
momentmaker
added a commit
that referenced
this pull request
Apr 8, 2024
…ersion * develop: (32 commits) [KS-136] Write target fixes (#12743) chore/release 2.10.0 to develop (#12740) [KS-136] Disallow non-trigger steps with no dependent ref (#12742) [KS-136] Correctly handle numbers in YAML by converting them to floats or ints (#12739) New log buffer (#12357) [KS-101] Add OCR3 capability contract wrapper (#12404) core/services/relay/evm: switch RequestRound DB & Tracker to use sqlutil.DataSource (#12706) Unregister filters for old coordinator contracts contract addresses from Functions LogPollerWrapper (#12696) Add table support for capability "type" property (#12622) Backout CRIB setup on develop. (#12705) fix node upgrade test (#12702) Reduces changeset scope to `minor` for semver (#12699) rm oz dep (#12700) @chainlink.contracts release v1.0.0 (#11714) feat: contracts publishing in CI (#12102) Bump default PG conns from 20->100; enable auto-scaling open conns for mercury (#12697) chore: chainlink-github-actions/* to v2.3.10 (#12694) LOOPP plugin config validation service (#12430) [TT-924] Migrate functions load tests to Seth (#12659) Enhance automation test config (AUTO-9430) (#12689) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Workflow for publishing contracts to NPM through CI.
Major changes in process
contracts-vX.Y.Z-.+
contracts-vX.Y.Z
--publish-branch <branch>
(as was done manually)--publish-branch
is for making surenpm publish
is only executed at the specified branch, this safe-guard is nolonger applicable because
--publish-branch
and--no-git-checks
duringpublish-prod
publish-prod
relies ondist-tag add
which essentially switches the npm release tagged withbeta
, and tagging it withlatest
. The--publish-branch
and--no-git-checks
do not apply to thenpm dist-tag add
command, only to thenpm publish
commandbeta
/pre
releaseTesting
Tested in separate (forked chainlink) repository with minimum content to reproduce contract builds.
Left to do:
RE-2226