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: Added service readiness check in add_service and add_services instructions, through the ServiceConfig.ReadyConditions field #148

Merged
merged 121 commits into from
Mar 20, 2023

Conversation

leoporoli
Copy link
Contributor

@leoporoli leoporoli commented Mar 13, 2023

Changelog picked up from commits here:

build(deps): bump github.com/docker/distribution from 2.7.1+incompatible to 2.8.0+incompatible in /core/server (#114)
build(deps): bump github.com/docker/distribution in /core/server
build(deps): bump github.com/opencontainers/image-spec from 1.0.1 to 1.0.2 in /core/server (#113)
build(deps): bump github.com/opencontainers/image-spec in /core/server
docs: add onboarding calendly links to docs (#14)
docs: create guide on installing historical versions (#131)
fix: fix changelog for versioned docs going forward (#142)
docs: pruned versions 0.68.1, 0.68.3 & 0.68.4 as the binaries were
docs: added changelog to 0.68.2, 0.68.5 & 0.68.6
docs: ignore docs built by docusaurus in docs checker (#141)
fix: sort services by name (#139)
fix: gramatical fix in analytics tracking logging (#138)
docs: Minify README language (#107)
chore(main): release 0.68.6 (#132)
docs: add kurtosis feedback cli command (#53)
feat: Added kurtosis feedback CLI command (#28)
docs: Simplify the docs landing page with latest "distribution application development platform" language (#110)
feat: publish versioned brew formula (#130)
build: Stop publishing go module to a separate repository (#124)
chore(main): release 0.68.5 (#128)
fix: Use version.txt for kurtosis_version instead of Git tags (#126)
chore(main): release 0.68.4 (#123)
fix: Pass correct latest tag to GoReleaser CLI build (#122)
chore(main): release 0.68.3 (#121)
feat: Use semver versioning for Golang API package (#119)
docs: remove WARN level log lines in readme (#112)
docs: add questions+help+feedback links (#111)
fix: remove mentions about github discussions (#95)
chore(main): release 0.68.2 (#120)
fix: fix push_cli_artifacts ci job (#118)
chore(main): release 0.68.1 (#115)
ci: fix push docs ci (#116)
feat: docs are versioned (#106)
refactor: remove dependence on private free ip address provider (#108)
refactor: Migrate IP Address and Hostname to runtime value (#100)
build(deps): bump golang.org/x/net from 0.0.0-20210913180222-943fd674d43e to 0.7.0 in /internal_testsuites/golang (#72)
build(deps): bump golang.org/x/net in /internal_testsuites/golang
docs: Fix NGINX port in quickstart (#109)
chore(main): release 0.68.0 (#102)
refactor!: Migrate Kurtosis Print instruction to Starlark framework. This restrict the use of print to a single argument only. (#80) (#87)
docs: fix a typo in exec assert example (#103)
docs: Add LICENSE (#99)
feat: enclave clean has both name and uuid (#101)
refactor: Migrate ConnectionConfig to Starlark Framework (#97)
refactor: Migrate packet delay distributions to Starlark Framework (#96)
refactor: Migrate PortSpec to Starlark Command Framework (#91)
feat: persist partition connection overrides to disk (#98)

@leoporoli leoporoli requested a review from gbouv March 16, 2023 21:06
Copy link
Contributor

@gbouv gbouv left a comment

Choose a reason for hiding this comment

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

Yup code looks good! Few small suggestions but don't block on them if you disagree

@gbouv
Copy link
Contributor

gbouv commented Mar 17, 2023

BTW why is this a breaking change?? Aren't the readiness checks optional after all?

@leoporoli
Copy link
Contributor Author

@gbouv yes it's not a breaking change, but it depends on the code that is in the breaking change branch now, which is not having the service_name in the recipe. I mean I'm adding this to the breaking change just to organize the release order, but I could use main as the base branch and merge it after 2023-03-22

@leoporoli leoporoli force-pushed the lporoli/740 branch 2 times, most recently from 3c61e5c to a28e1cd Compare March 20, 2023 12:49
@leoporoli leoporoli merged commit 13a9c63 into 2023-03-22-breaking-release Mar 20, 2023
@leoporoli leoporoli deleted the lporoli/740 branch March 20, 2023 13:29
@leeederek
Copy link
Contributor

Do we have some docs on this @leoporoli ? This feels user-facing

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.

8 participants