release

Automate version bumps, compatibility updates, and Julia package releases.

40|12|Updated Sep 1, 2021
One-click install
npx skills add https://github.com/PTsolvers/JustRelax.jl --skill release-ptsolvers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/PTsolvers/JustRelax.jl/tree/main/.claude/skills/release
Command: npx skills add https://github.com/PTsolvers/JustRelax.jl --skill release-ptsolvers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the release process for new versions of JustRelax.jl, including version bumps, compatibility updates, and deployment to the Julia General registry.

Core Features & Use Cases

  • Version Bumping: Automatically increments version numbers in Project.toml based on SemVer practices.
  • Compatibility Updates: Ensures [compat] entries are up-to-date with tightly-coupled packages.
  • CI/CD Integration: Validates CI/CD pipeline status before proceeding with the release.
  • Tag Creation: Utilizes JuliaRegistrator and TagBot to create and manage release tags.

Quick Start

Run the release skill to prepare and execute the release of a new version of JustRelax.jl.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate Julia package release deployment to the General registry?

This Skill automates version bumping in Project.toml, updates compatibility entries, and deploys releases to the Julia General registry using JuliaRegistrator and TagBot.

Can I publish a new Julia package version if my CI/CD pipeline is failing?

You cannot publish a new Julia package version with a failing CI/CD pipeline. The release automation process validates and requires a green CI/CD status before proceeding with deployment.

How does version bumping work for Julia packages following SemVer practices?

Version bumping for Julia packages automatically increments version numbers in Project.toml based on SemVer practices, ensuring compatibility entries are up-to-date with tightly-coupled packages before release.

Do I need JuliaRegistrator and TagBot to automate Julia package tag creation?

Yes, JuliaRegistrator and TagBot are required dependencies for this release automation process, used to register packages and automatically create and manage release tags in the Julia ecosystem.

What is the best way to update compatibility entries for tightly-coupled Julia packages?

The best way to update compatibility entries for tightly-coupled Julia packages is through release automation, which ensures [compat] entries in Project.toml are up-to-date before deploying a new version.

Why does my automated Julia package release require a green CI/CD pipeline status?

An automated Julia package release requires a green CI/CD pipeline status to ensure code stability, as the release process validates pipeline success before proceeding with version bumping and tag creation.