القائمة
Releasing a new JustRelax.jl version — version bumps, compat bumps, JuliaRegistrator, TagBot. Use when preparing or asked about a release.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
How JustRelax.jl handles CPU/CUDA/AMDGPU backends — module structure, package extensions, ParallelStencil initialization rules. Use when adding/modifying kernels or anything device-related.
ParallelStencil kernel idioms and GPU-compatibility rules for JustRelax.jl, plus the Runic formatting requirement. Use when writing or editing compute kernels or any Julia source.
How to run JustRelax.jl tests — single files, the full ParallelTestRunner suite, backend selection, and MPI tests. Use whenever running or debugging tests.
Building and editing JustRelax.jl documentation (Documenter + DocumenterVitepress). Use when changing docs, docstrings, or the docs build.
How to run JustRelax.jl miniapps (benchmarks, convection, subduction) to validate solver/physics changes end-to-end. Use when verifying a physics change beyond unit tests.
| name | release |
| description | Releasing a new JustRelax.jl version — version bumps, compat bumps, JuliaRegistrator, TagBot. Use when preparing or asked about a release. |
JustRelax.jl is registered in the Julia General registry. Releases are driven from main.
Bump version in Project.toml (currently 0.x — patch for fixes, minor for features/breaking, per common 0.x SemVer practice in the Julia ecosystem).
Make sure [compat] entries are current. The tightly-coupled companion packages are GeoParams and JustPIC (both PTsolvers); a JustRelax release often follows a compat bump for one of these. Dependabot handles GitHub Actions, not Julia compat — compat bumps are manual or via CompatHelper-style PRs.
Ensure CI is green on main, including the CSCS GPU pipeline if solver code changed.
On the GitHub commit of the version bump (after merge to main), comment:
@JuliaRegistrator register
JuliaRegistrator opens the General registry PR; once merged, TagBot (.github/workflows/TagBot.yml) creates the GitHub tag/release automatically. Do not create tags by hand.
CITATION.cff has its own validation workflows (cff-validator.yml, validate_zenodo.yml); update it if authors change. A release also triggers Zenodo archiving via the repo's Zenodo integration.@JuliaRegistrator register comment via Release notes: block).