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

fix: npm publish order #2687

Merged
merged 1 commit into from
Oct 4, 2023
Merged

fix: npm publish order #2687

merged 1 commit into from
Oct 4, 2023

Conversation

spypsy
Copy link
Member

@spypsy spypsy commented Oct 4, 2023

Need to publish npm packages that other depend on first

Checklist:

Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

  • If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
  • I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
  • Every change is related to the PR description.
  • I have linked this pull request to relevant issues (if any exist).

@spypsy spypsy changed the title fix: npm deploy order fix: npm publish order Oct 4, 2023
@PhilWindle PhilWindle enabled auto-merge (squash) October 4, 2023 15:52
@PhilWindle PhilWindle merged commit 876c0b1 into master Oct 4, 2023
3 checks passed
@PhilWindle PhilWindle deleted the spy/fix-npm-build-order branch October 4, 2023 15:54
spalladino pushed a commit that referenced this pull request Oct 4, 2023
🤖 I have created a release *beep* *boop*
---


<details><summary>aztec-packages: 0.8.5</summary>

##
[0.8.5](aztec-packages-v0.8.4...aztec-packages-v0.8.5)
(2023-10-04)


### Bug Fixes

* Ensure resources ignition directory exists
([#2684](#2684))
([f4f2cd0](f4f2cd0))
* Include resources folder in circuits.js package.json
([#2689](#2689))
([34ed2c2](34ed2c2))
* Npm publish order
([#2687](#2687))
([876c0b1](876c0b1))
</details>

<details><summary>barretenberg.js: 0.8.5</summary>

##
[0.8.5](barretenberg.js-v0.8.4...barretenberg.js-v0.8.5)
(2023-10-04)


### Miscellaneous

* **barretenberg.js:** Synchronize aztec-packages versions
</details>

<details><summary>barretenberg: 0.8.5</summary>

##
[0.8.5](barretenberg-v0.8.4...barretenberg-v0.8.5)
(2023-10-04)


### Miscellaneous

* **barretenberg:** Synchronize aztec-packages versions
</details>

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
AztecBot added a commit to AztecProtocol/barretenberg that referenced this pull request Oct 5, 2023
🤖 I have created a release *beep* *boop*
---


<details><summary>aztec-packages: 0.8.5</summary>

##
[0.8.5](AztecProtocol/aztec-packages@aztec-packages-v0.8.4...aztec-packages-v0.8.5)
(2023-10-04)


### Bug Fixes

* Ensure resources ignition directory exists
([#2684](AztecProtocol/aztec-packages#2684))
([f4f2cd0](AztecProtocol/aztec-packages@f4f2cd0))
* Include resources folder in circuits.js package.json
([#2689](AztecProtocol/aztec-packages#2689))
([34ed2c2](AztecProtocol/aztec-packages@34ed2c2))
* Npm publish order
([#2687](AztecProtocol/aztec-packages#2687))
([876c0b1](AztecProtocol/aztec-packages@876c0b1))
</details>

<details><summary>barretenberg.js: 0.8.5</summary>

##
[0.8.5](AztecProtocol/aztec-packages@barretenberg.js-v0.8.4...barretenberg.js-v0.8.5)
(2023-10-04)


### Miscellaneous

* **barretenberg.js:** Synchronize aztec-packages versions
</details>

<details><summary>barretenberg: 0.8.5</summary>

##
[0.8.5](AztecProtocol/aztec-packages@barretenberg-v0.8.4...barretenberg-v0.8.5)
(2023-10-04)


### Miscellaneous

* **barretenberg:** Synchronize aztec-packages versions
</details>

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Maddiaa0 pushed a commit that referenced this pull request Oct 6, 2023
Need to publish npm packages that other depend on first

# Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if
the PR is ready to merge.
- [ ] If the pull request requires a cryptography review (e.g.
cryptographic algorithm implementations) I have added the 'crypto' tag.
- [ ] I have reviewed my diff in github, line by line and removed
unexpected formatting changes, testing logs, or commented-out code.
- [ ] Every change is related to the PR description.
- [ ] I have
[linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)
this pull request to relevant issues (if any exist).
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.

2 participants