Skip to content

Commit

Permalink
chore(main): release 0.13.0 (#271)
Browse files Browse the repository at this point in the history
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
  • Loading branch information
github-actions[bot] authored May 14, 2024
1 parent 6404aa0 commit a52d777
Show file tree
Hide file tree
Showing 4 changed files with 21 additions and 4 deletions.
2 changes: 1 addition & 1 deletion .release-please-manifest.json
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
{
".": "0.12.1"
".": "0.13.0"
}
17 changes: 17 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,22 @@
# Changelog

## [0.13.0](https://github.com/launchdarkly/ldcli/compare/v0.12.1...v0.13.0) (2024-05-14)


### Features

* track setup completed ([#272](https://github.com/launchdarkly/ldcli/issues/272)) ([6554b7d](https://github.com/launchdarkly/ldcli/commit/6554b7d5ca29c59ca089b755b8a925d7065cfca7))


### Bug Fixes

* add back member invite alias ([#276](https://github.com/launchdarkly/ldcli/issues/276)) ([a5d0a8c](https://github.com/launchdarkly/ldcli/commit/a5d0a8c032d57d1e685edc52ad22feafa41ff6b3))
* Fix typo in README ([#278](https://github.com/launchdarkly/ldcli/issues/278)) ([6404aa0](https://github.com/launchdarkly/ldcli/commit/6404aa05b5bd875e5116b880d1629536a6489bde))
* fix viewport ([#280](https://github.com/launchdarkly/ldcli/issues/280)) ([d079561](https://github.com/launchdarkly/ldcli/commit/d079561f63b284da9025611eb74a06c36cc41e8e))
* remove bad template func ([#275](https://github.com/launchdarkly/ldcli/issues/275)) ([5de0112](https://github.com/launchdarkly/ldcli/commit/5de0112cb21d0662c9c58a0bc41ea41623f6a7eb))
* toggle flag aliases ([#269](https://github.com/launchdarkly/ldcli/issues/269)) ([76de2a5](https://github.com/launchdarkly/ldcli/commit/76de2a5f85e84dcaf2e64e27820c85205aebf650))
* update usage template to only show flags when present ([#273](https://github.com/launchdarkly/ldcli/issues/273)) ([68e6b5c](https://github.com/launchdarkly/ldcli/commit/68e6b5ce6684075b07ae7958f375eeed3ce29780))

## [0.12.1](https://github.com/launchdarkly/ldcli/compare/v0.12.0...v0.12.1) (2024-05-10)


Expand Down
4 changes: 2 additions & 2 deletions PROVENANCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,15 +5,15 @@ LaunchDarkly uses the [SLSA framework](https://slsa.dev/spec/v1.0/about) (Supply
As part of [SLSA requirements for level 3 compliance](https://slsa.dev/spec/v1.0/requirements), LaunchDarkly publishes provenance about our package builds using [GitHub's generic SLSA3 provenance generator](https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/generic/README.md#generation-of-slsa3-provenance-for-arbitrary-projects) for distribution alongside our packages.

<!-- x-release-please-start-version -->
These attestations are available for download from the GitHub release page for the release version under Assets > `ldcli_0.12.1_multiple_provenance.intoto.jsonl`.
These attestations are available for download from the GitHub release page for the release version under Assets > `ldcli_0.13.0_multiple_provenance.intoto.jsonl`.
<!-- x-release-please-end -->

To verify SLSA provenance attestations, we recommend using [slsa-verifier](https://github.com/slsa-framework/slsa-verifier). Example usage for verifying packages for Linux is included below:

<!-- x-release-please-start-version -->
```
# Set the version of the PACKAGE to verify
PACKAGE_VERSION=0.12.1
PACKAGE_VERSION=0.13.0
```
<!-- x-release-please-end -->

Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "@launchdarkly/ldcli",
"description": "The official command line interface for managing LaunchDarkly feature flags.",
"version": "0.12.1",
"version": "0.13.0",
"main": "index.js",
"scripts": {
"postinstall": "go-npm install",
Expand Down

0 comments on commit a52d777

Please sign in to comment.