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

feat: deploy l1 contracts npm pkg #2754

Merged
merged 5 commits into from
Oct 11, 2023
Merged

Conversation

rahul-kothari
Copy link
Contributor

@rahul-kothari rahul-kothari commented Oct 10, 2023

Introducing https://www.npmjs.com/package/@aztec/l1-contracts
I have manually deployed v0.8.8 (since deploy-npm script works for continual releases). Next release onwards CI should release 0.8.9 automatically!

Also created a README so people don't struggle as much!

Thanks @ludamad @PhilWindle for the help!

@rahul-kothari rahul-kothari changed the title deploy l1 contracts npm pkg feat: deploy l1 contracts npm pkg Oct 10, 2023
.circleci/config.yml Outdated Show resolved Hide resolved

function deploy_package() {
REPOSITORY=$1
cd $REPOSITORY

VERSION=$(extract_tag_version $REPOSITORY true)
VERSION=$(extract_tag_version $REPOSITORY false)
Copy link
Contributor

Choose a reason for hiding this comment

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

Why is this one changed? Should it not error if failing anymore?

Copy link
Collaborator

Choose a reason for hiding this comment

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

The idea is to be able to take in this without a tag and see the entire process dry run. Open to thoughts here but this was changed by me then back by @spalladino . This reverts to my intended change allowing dry runs

Copy link
Contributor

Choose a reason for hiding this comment

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

So it should be false? @ludamad (remember I'm peanut-brain, so I just need a simple yes/no here 🥜).

Copy link
Contributor Author

@rahul-kothari rahul-kothari Oct 10, 2023

Choose a reason for hiding this comment

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

yeap - without it, you can't do dry runs

Copy link
Collaborator

Choose a reason for hiding this comment

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

Ahh good to know, I wasn't aware that that was the intention. Makes sense then!

# Generate L1 contract TypeScript artifacts.
COPY --from=contracts /usr/src/l1-contracts/out /usr/src/l1-contracts/out
Copy link
Contributor

Choose a reason for hiding this comment

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

Why remove this one? Were they redundant with the generate-artifacts.sh?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No now that we are copying the entire l1-contracts, out directory gets copied with it. So this line is not needed anymore

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah yes, I forgot to think.

@rahul-kothari rahul-kothari enabled auto-merge (squash) October 10, 2023 15:33
@rahul-kothari rahul-kothari merged commit e317c47 into master Oct 11, 2023
3 checks passed
@rahul-kothari rahul-kothari deleted the rk/deploy_l1_contracts branch October 11, 2023 08:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

5 participants