Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The commit tagged as v1.8.1 was faulty (as it hadn't updated `defconst cider-version`).
- Loading branch information
Showing
2 changed files
with
3 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,7 +2,7 @@ | |
|
||
## master (unreleased) | ||
|
||
## 1.8.1 (2023-10-15) | ||
## 1.8.2 (2023-10-15) | ||
|
||
### Changes | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
0f689fd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would have still been better to keep the faulty commit/release around, otherwise the release numbering looks somewhat weird. Anyways, not a big deal.
0f689fd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 1.18.1 tag was faulty because I had forgotten to indicate that number at .el level.
I didn't go as far as removing the commit, but yeah it seemed noisy to have it in the changelog.