Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions packages/cli/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,14 @@
# Changelog

## [0.0.2](https://github.com/treyturner/ts-artifacts/compare/@trey.turner/artifacts-cli-v0.0.1...@trey.turner/artifacts-cli-v0.0.2) (2026-03-19)


### Dependencies

* The following workspace dependencies were updated
* dependencies
* @trey.turner/artifacts-api-client bumped to 1.1.1

## 0.0.1 (2024-10-07)


Expand Down
2 changes: 1 addition & 1 deletion packages/cli/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@trey.turner/artifacts-cli",
"version": "0.0.1",
"version": "0.0.2",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Update the release-please manifest with the new cli version

In the release workflow I checked (.github/workflows/release-publish.yaml:23-26), googleapis/release-please-action is driven by the repo manifest, but this commit only bumps packages/cli/package.json to 0.0.2 and leaves .release-please-manifest.json:4 at 0.0.1. On the next cli change, release-please will still treat 0.0.1 as the last released version, which can regenerate a duplicate 0.0.2 release/changelog instead of advancing from 0.0.2.

Useful? React with 👍 / 👎.

"module": "index.ts",
"main": "dist/index.js",
"types": "dist/types.d.ts",
Expand Down