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.

Sign up for GitHub

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

Jump to bottom

Release v4.2.0 #499

Merged
merged 1 commit into from
Aug 10, 2023
Merged

Release v4.2.0 #499

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
15 changes: 8 additions & 7 deletions CHANGES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,11 @@
## 4.5.0

* Drop support for rubies prior 2.2.10

## 4.1.8

* Fix ruby warning with undefined instance variable in codebase
## 4.2.0

* Add Ruby 3 support
* Use trailblazer-option over declarative-option and upgrade declarative-builder (#492)
* Use GitHub Actions over Travis as CI service
* Drop support for Rubies prior to 2.2.10 and remove custom OutputBuffer class (#475)
* Use Tilt::Cache instead of our own cache implementation (#470)
* Fix Ruby warning with undefined instance variables (#469)

## 4.1.7

Expand Down
2 changes: 1 addition & 1 deletion lib/cell/version.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
module Cell
VERSION = "4.5.0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Previous versioning here seems mess 😄 I'm wondering if anyone using 4.5.0 would be able to get updates from >= 4.2.0 & < 4.5.0.

Should we release incremental minor version instead ? cc @apotonick

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have not released 4.5.0, yet, have we not?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, not from rubygems but in case someone is using github repo in Gemfile directly ? I hope there shouldn't be any problems.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, but let's go with 4.2.0 and face the consequences 💥 😂

VERSION = "4.2.0"
end