jsr

Automate Deno package releases to JSR with Git tags and GitHub Actions.

2|Updated Aug 3, 2021
One-click install
npx skills add https://github.com/kuboon/dotfiles --skill jsr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jsr
Source: https://github.com/kuboon/dotfiles/tree/main/skills/jsr
Command: npx skills add https://github.com/kuboon/dotfiles --skill jsr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the release workflow for Deno-based projects by updating versioning, tagging, and publishing to the JavaScript Registry (JSR) automatically.

Core Features & Use Cases

  • Version bump automation: updates deno.json version and records the commit.
  • Git tagging and publishing: creates a git tag and triggers deno publish.
  • CI-friendly workflow: supports GitHub Actions CI to run tests and release on main pushes.

Quick Start

Run the release task to bump the version, for example: deno task release 1.2.3

Frequently Asked Questions about jsr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Deno package publishing to JSR using GitHub Actions?

Automate Deno package publishing to JSR by running a release task that updates the deno.json version, commits the change, creates a Git tag, and triggers deno publish in your CI workflow.

What is the best way to bump versions and create Git tags for a Deno project?

The best way to bump versions and create Git tags is to run a release script that updates your deno.json version, records the commit, and automatically creates a Git tag for that release.

Can I trigger deno publish automatically when pushing to the main branch?

Yes, you can trigger deno publish automatically on main pushes by integrating this release workflow with your GitHub Actions CI to run tests and publish new versions.

How does the deno.json version update and release process work?

The deno.json version update process works by executing a command like deno task release 1.2.3, which modifies the version field, commits the file change, and tags the release for CI publishing.

What do I need to set up before automating Deno releases to JSR?

Before automating Deno releases to JSR, you need a Deno project using Git for version control and GitHub Actions configured to run your CI tests and trigger the publishing workflow.