Skip to content

DeepSeek release-prep: Add alpha release prep #21

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.

Sign up for GitHub

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

Closed
localhost41 wants to merge 1 commit into from
Closed

DeepSeek release-prep: Add alpha release prep #21

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 2 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

## Unreleased

- Alpha release readiness checks and documentation.

## v0.1.0-alpha.1 - 2025-01-30

- Initial repository scaffold.
Expand Down
11 changes: 11 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,3 +127,14 @@ This will create a tarball (e.g., `localhostlabs-create-qvac-app-0.1.0-alpha.1.t
containing only the files listed in the `files` field of `package.json`.

CI runs the same health checks on pull requests and pushes to `main`.

## Alpha release readiness

- [x] Package version is `0.1.0-alpha.1` (alpha).
- [x] CHANGELOG includes release notes for `v0.1.0-alpha.1`.
- [x] `npm pack` builds successfully: run `pnpm build && npm pack`.
- [x] Metadata checks passing (package name, bin, main, files fields).

**Note:** The `"private": true` field prevents accidental publishing. When it is
time to publish, `--access public` must be used and the `private` field should
be removed or set to `false`.
Loading