Skip to content

Commit

Permalink
Merge pull request #17 from yihozhang/release-0.2.0
Browse files Browse the repository at this point in the history
Prepare v0.2.0
  • Loading branch information
yihozhang authored Sep 28, 2024
2 parents 3625e0d + af29e78 commit f303fe1
Show file tree
Hide file tree
Showing 3 changed files with 29 additions and 1 deletion.
16 changes: 16 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# Changes

## [Unreleased] - ReleaseDate

## [0.2.0] - 2024-9-??

New features

- Add support for storing if a node is subsumed (#16)
- Add ability to split e-classes for easier visualization (#14)
- Add ability to "saturate" `inline_leaves` (#6)
- Other minor improvements (#7,#8, #9, #10)

## [0.1.0] - 2023-10-27

The first version of the egraph-serialize library is released
2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ edition = "2021"
authors = ["Max Willsey <[email protected]>"]
description = "A library to serialize e-graphs"
name = "egraph-serialize"
version = "0.1.0"
version = "0.2.0"
repository = "https://github.com/egraphs-good/egraph-serialize"
keywords = ["e-graphs"]
license = "MIT"
Expand Down
12 changes: 12 additions & 0 deletions release-instructions.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
(Copied from `release-instructions.md` of `egraphs-good/egglog``)

How to do a release:
1. Update `CHANGELOG.md` with a new entry and new link at the bottom.
2. Find and replace in the codebase to update the version number. Make sure to get `Cargo.toml` and places in the changelog. Be careful not the screw up old links though!
4. Commit.
5. Tag the commit with the version number.
6. Make a PR and make sure the tag gets added.
7. Merge the PR
8. `cargo publish --dry-run`
1. Sometimes this can result in an error- you may need to run `cargo update` to update `cargo.lock`
9. `cargo publish`

0 comments on commit f303fe1

Please sign in to comment.