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

Cut a new CLI release #1066

Merged
merged 13 commits into from
Aug 22, 2024
Merged

Cut a new CLI release #1066

merged 13 commits into from
Aug 22, 2024

Conversation

christian-stephen
Copy link
Contributor

@christian-stephen christian-stephen commented Aug 15, 2024

Checklist

=========

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have checked for similar issues and haven't found anything relevant.
  • This is not a security issue (which should be reported here: https://circleci.com/security/)
  • I have read Contribution Guidelines.

Internal Checklist

  • I am requesting a review from my own team as well as the owning team
  • I have a plan in place for the monitoring of the changes that I am making (this can include new monitors, logs to be aware of, etc...)

Changes

=======

Rationale

=========

What was the overarching product goal of this PR as well as any pertinent
history of changes

Considerations

==============

Why you made some of the technical decisions that you made, especially if the
reasoning is not immediately obvious

Screenshots

============

Before

Image or [gif](https://giphy.com/apps/giphycapture)

After

Image or gif where change can be clearly seen

Here are some helpful tips you can follow when submitting a pull request:

  1. Fork the repository and create your branch from main.
  2. Run make build in the repository root.
  3. If you've fixed a bug or added code that should be tested, add tests!
  4. Ensure the test suite passes (make test).
  5. The --debug flag is often helpful for debugging HTTP client requests and responses.
  6. Format your code with gofmt.
  7. Make sure your code lints (make lint). Note: This requires Docker to run inside a local job.

@christian-stephen christian-stephen marked this pull request as ready for review August 15, 2024 18:07
@christian-stephen christian-stephen requested review from a team as code owners August 15, 2024 18:07
@niubrandon niubrandon requested a review from a team as a code owner August 21, 2024 12:36
There has been a change to how configs are compiled that makes this test
invalid.

Previously we would allow any random owner ID to be passed in
when compiling certified orbs as these were enabled by default and
didn't require any checks with the provided owner ID.

To support an upcoming feature, now when compiling the config, all
provided owner IDs are checked and must exist to validate that the
organization allows that type of orb.

The CLI can continue to use no owner ID with public certified orbs as
tested in the above case.

https://github.com/CircleCI-Public/circleci-cli/blob/2766f0e710c8727e346e247f6c779079a79b010c/integration_tests/features/circleci_config.feature#L63-L85
…lidate-test

PIPE-4877 Remove config validate test with invalid org ID
@christian-stephen christian-stephen merged commit 43103be into main Aug 22, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants