Skip to content

Commit f31d2d7

Browse files
committed
Update AGENTS.md
1 parent bfa6c92 commit f31d2d7

1 file changed

Lines changed: 6 additions & 4 deletions

File tree

AGENTS.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ To run a single test file with a specific filter:
5656

5757
```bash
5858
deno task build
59-
test -A --no-lock test/<name>.test.tsx --filter "<search>"
59+
deno test -A --no-lock test/<name>.test.tsx --filter "<search>"
6060
```
6161

6262
## Linting and formatting
@@ -72,9 +72,11 @@ Publishing is automated by GitHub Actions on `main` when a version tag is pushed
7272

7373
When the user asks to publish a new version:
7474

75+
0. Run `deno task test` first, **if the tests fail, stop the process and notify the user.**
7576
1. Check the current version in `package.json`.
7677
2. Show the user a selectable list of possible next versions, ask the user to choose which one to publish.
7778
3. After the user confirms the target version, update both `package.json` and `version.ts`.
78-
4. Commit only the release-related changes with the message "chore: Bump package version to v<new-version>".
79-
5. Create a git tag named `v<new-version>` on that commit.
80-
6. Show the user a prompt window to confirm the publish action, and if the user confirms, push both the commit and tag to the remote repository.
79+
4. Run `deno task build` to build the package dist.
80+
5. Commit only the release-related changes with `git commit -m "chore: bump package version to v<new-version>"`.
81+
6. Create a git tag named `v<new-version>` on that commit.
82+
7. Show the user a prompt window to confirm the publish action, and if the user confirms, push both the commit and tag to the remote repository.

0 commit comments

Comments
 (0)