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

chore(noir): Release 0.2.0 #769

Merged
merged 2 commits into from
Feb 16, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Feb 8, 2023

🤖 I have created a release beep boop

0.2.0 (2023-02-16)

⚠ BREAKING CHANGES

  • Make abi field non-optional in CompiledProgram (#856)
  • nargo: bump MSRV to 1.66.0 (#799)

Features

Bug Fixes

  • avoid testing equality between unit values in acir_gen test (#849) (c2b7230)
  • ci: Skip the title check if handling a merge group (#790) (71b179c)
  • nargo: nargo test now only runs test functions defined in the current module (#805) (c6293c9)
  • operators issuing type errors when used with matching integer types arising from generic code (#789) (932943a)
  • ssa: delete instructions with false predicate (#760) (f329379)
  • ssa: synchronisation for functions (#764) (615357a)

Miscellaneous Chores


This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--master--components--noir branch 5 times, most recently from d8e298b to 54dc062 Compare February 10, 2023 09:18
@github-actions github-actions bot changed the title chore(noir): Release 0.1.2 chore(noir): Release 0.2.0 Feb 10, 2023
@github-actions github-actions bot force-pushed the release-please--branches--master--components--noir branch 9 times, most recently from f815400 to 6671fe6 Compare February 13, 2023 17:10
@kevaundray kevaundray force-pushed the release-please--branches--master--components--noir branch 6 times, most recently from f3c38f7 to 37b3b92 Compare February 15, 2023 16:35
Copy link
Contributor

@jfecher jfecher left a comment

Choose a reason for hiding this comment

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

What is our policy for reviewing these PRs? Should we wait a set amount of time before approving them? Should we wait for certain other PRs to be merged beforehand?

@kevaundray kevaundray force-pushed the release-please--branches--master--components--noir branch 3 times, most recently from 89a3807 to 2f409b5 Compare February 16, 2023 18:35
@kevaundray
Copy link
Contributor

What is our policy for reviewing these PRs? Should we wait a set amount of time before approving them? Should we wait for certain other PRs to be merged beforehand?

I don't think they require a review, but maybe I misunderstand what you mean -- For now I've been going off of breaking changes for Noir.

We should make it weekly, so that we build up the muscle memory for pushing releases though imo

@kevaundray kevaundray force-pushed the release-please--branches--master--components--noir branch from 3494826 to f7eaaac Compare February 16, 2023 19:50
@kevaundray kevaundray force-pushed the release-please--branches--master--components--noir branch from a7adb26 to 1a09187 Compare February 16, 2023 20:48
@kevaundray kevaundray added this pull request to the merge queue Feb 16, 2023
Merged via the queue into master with commit ca986a4 Feb 16, 2023
@kevaundray kevaundray deleted the release-please--branches--master--components--noir branch February 16, 2023 22:21
@kevaundray
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants