Skip to content

gtk-rs/release

master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
src
 
 
 
 
 
 
 
 
 
 

Release process

Since gtk-rs has multiple crates which have inter-dependencies, it's a bit painful to make a new release. So here are the multiple steps:

  • Get the current version for all crates (all crates in one repository should all have the same!).
  • Replace git dependencies with crates.io ones.
  • Push those changes to a branch with MAJOR.MEDIUM name.
  • Push tags.
  • Write a blog post (add the file into _posts folder in gtk-rs.github.io repository) announcing the new release.
  • Publish crates.
  • Update dev branch crates' version.

Note that the github token is used for two things:

  1. Gathering the merged pull requests.
  2. Opening pull requests (for the version updates).

Using this tool

I don't recommend it if you're not a member of the gtk-rs organization but just in case:

python3 src/release.py -m MEDIUM -t [Your github token here]

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Sponsor this project

Packages

No packages published

Languages