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

Release 5.6.0 #415

Merged
merged 24 commits into from
Jun 22, 2023
Merged

Release 5.6.0 #415

merged 24 commits into from
Jun 22, 2023

Conversation

malparty
Copy link
Member

tyrro and others added 24 commits March 30, 2023 16:07
…build-commands

[#348] Add Makefile to build commands
[#404] Fix: Loaderror: cannot load such file -- sassc when generating the project from the template
[gh385] Minify the CSS and JS for production build
@malparty malparty added this to the 5.6.0 milestone Jun 22, 2023
@malparty malparty self-assigned this Jun 22, 2023
@malparty malparty marked this pull request as ready for review June 22, 2023 03:23
@hoangmirs
Copy link
Contributor

The PR title should be Release - 5.6.0 🙏

@@ -9,6 +9,7 @@ gem 'mini_magick' # A ruby wrapper for ImageMagick or GraphicsMagick command lin
gem 'pagy' # A pagination gem that is very light and fast
gem 'discard' # Soft deletes for ActiveRecord
gem 'sidekiq' # background processing for Ruby
gem 'sassc' # bootsnap dependency
Copy link
Member

Choose a reason for hiding this comment

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

I'm sorry about this comment, which is a bit late but I'm not sure about this gem, it's an old gem (last update was 2020) and I remember SASS in C was deprecated, the SASS team moved to the DartSass already, and we don't use this gem in the generated project at all....

Maybe this gem is needed during generating the new project, but later on we don't use it, should we remove it at the end? with a post setup callback? cc @sanG-github

Copy link
Contributor

Choose a reason for hiding this comment

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

I agree with the above statement, but it would be best to move this concern into an issue to address it in the next release.

Copy link
Contributor

Choose a reason for hiding this comment

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

That's appropriate, but as far as I remember, we still need it to run the project, not only generating it.
In that case, I think we need to use another alternative. (Note that this one was caused by the bootsnap gem)

Copy link
Member

Choose a reason for hiding this comment

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

Maybe a solution is just creating a new issue to remove this gem :D so all good with this release cc @malparty

Copy link
Member Author

Choose a reason for hiding this comment

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

This is the actual bug fix that prevented to use the Template :harold:

yes, I'll create an issue 🙇

Copy link
Member Author

Choose a reason for hiding this comment

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

#416

@malparty malparty changed the title Release/5.6.0 Release 5.6.0 Jun 22, 2023
@malparty malparty changed the title Release 5.6.0 Release - 5.6.0 Jun 22, 2023
@malparty malparty merged commit 2265237 into main Jun 22, 2023
@malparty malparty deleted the release/5.6.0 branch June 22, 2023 04:05
@malparty malparty changed the title Release - 5.6.0 Release 5.6.0 Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants