Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix date in changelog for fs-sim-0.2.1.0. #36

Merged
merged 1 commit into from
Aug 1, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 0 additions & 10 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,13 +55,3 @@ like `A.B.C.D`.
* `C` is the *minor* version number. A bump indicates a non-breaking change.
* `D` is the *patch* version number. A bump indicates a small, non-breaking
patch.

To prevent accidental breakage for downstream packages, `fs-api` and `fs-sim`
should be released in lockstep with respect to major version bumps. This means
that a major version bump for `fs-api` should result in a major version bump for
`fs-sim`, and vice versa. `fs-api` and `fs-sim` can be released invidivually
when only minor or patch version numbers are bumped. Preferably, `fs-sim-x.y.*`
should have a caret bound on `fs-api-x.y.*`, i.e., `^>= fs-api-x.y`

NOTE: before `fs-sim-0.3.*` and `fs-api-0.3.*`, both packages were not released
in lockstep.
2 changes: 1 addition & 1 deletion fs-sim/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Revision history for fs-sim

## 0.2.1.0 -- 2023-06-02
## 0.2.1.0 -- 2023-08-01

### Non-breaking

Expand Down