Skip to content

chore(main): release kurtosis 2.0.0#2589

Closed
kurtosisbot wants to merge 2 commits intomainfrom
release-please--branches--main--components--kurtosis
Closed

chore(main): release kurtosis 2.0.0#2589
kurtosisbot wants to merge 2 commits intomainfrom
release-please--branches--main--components--kurtosis

Conversation

@kurtosisbot
Copy link
Contributor

🤖 I have created a release beep boop

2.0.0 (2024-11-01)

⚠ BREAKING CHANGES

  • release version 1 (#2487)
  • change license to apache 2.0 (#2481)
  • copy contents of directory instead of the directory if store is used for directories (#2326)
  • remove the cloud add and CreateCloudInstance endpoint (#2234)
  • change registry spec to imagespec (#2191)
  • allow to mount multiple artifacts to the same folder in a service. Users will need to replace the Directory.artifac_name field key with Directory.artifac_names (#2025)
  • change persistent directory name to deterministic value (#2006)

Features

Bug Fixes

Miscellaneous Chores

  • remove the cloud add and CreateCloudInstance endpoint (#2234) (0f17729)

This PR was generated with Release Please. See documentation.

@skylenet skylenet closed this Nov 1, 2024
github-merge-queue bot pushed a commit that referenced this pull request Nov 1, 2024
## Description
<!-- Describe this change, how it works, and the motivation behind it.
-->
We need to remove the component from the release now. It made a [2.0.0
PR](#2589) because it
thinks it's a new component named "kurtosis" . We need to remove that
component prefix. Then it should be able to pickup previous releases and
not create a 2.0.0 .. which it's now creating because it's ignoring all
past releases due to it thinking that it's a new component (app)
## REMINDER: Tag Reviewers, so they get notified to review

## Is this change user facing?
NO
<!-- If yes, please add the "user facing" label to the PR -->
<!-- If yes, don't forget to include docs changes where relevant -->

## References (if applicable)
<!-- Add relevant Github Issues, Discord threads, or other helpful
information. -->
<!-- You can auto-close issues by putting "Fixes #XXXX" here. -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment