Skip to content

docs: mention deno.json(c) in publishing from GitHub #1062

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

Merged
merged 1 commit into from
Apr 30, 2025
Merged
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
6 changes: 3 additions & 3 deletions frontend/docs/publishing-packages.md
Original file line number Diff line number Diff line change
Expand Up @@ -346,9 +346,9 @@ jobs:

This workflow will run every time you push to the `main` branch of your
repository. It will publish your package to JSR, and will automatically use the
correct version number based on the version in your `jsr.json` file.
`jsr publish` will not attempt to publish if the version specified in your
`jsr.json` file is already published to JSR.
correct version number based on the version in your `jsr.json`/`deno.json(c)`
file. `jsr publish` will not attempt to publish if the version specified in your
`jsr.json`/`deno.json(c)` file is already published to JSR.

## Filtering files

Expand Down
Loading