Create a `release.yml` or similar CI job to automate releases

Open
  • Is something wrong?
#61 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions
Domain
devops, release

Research direction

The issue asks for a new GitHub Actions workflow, probably a release.yml, under the repository's workflow directory. Start with RELEASING.md, which the issue points to, to learn the manual release steps and the rule that CIP112 token releases must ship Apache-2.0 license files. Done means a workflow that reproduces those steps and checks for the license files, and that a maintainer can validate on a test tag.

Written by the indexing model from the issue text.

Description

Note that CIP112 token-related releases must include Apache-2.0 license files.
Check RELEASING.md for more information.

Dominant language
Haskell
Stars
5
Forks
0
Avg merge
1d 36m
Merged PRs (30d)
11

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenZeppelin/canton-contracts

All issues in OpenZeppelin/canton-contracts

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.