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

Update rubocop #336

Closed
difernandez opened this issue Jan 28, 2021 · 0 comments · Fixed by #337
Closed

Update rubocop #336

difernandez opened this issue Jan 28, 2021 · 0 comments · Fixed by #337
Assignees

Comments

@difernandez
Copy link
Contributor

In october Rubocop finally released v1.0, their first stable version 🎉 :

The big news for end users and maintainers of extensions is that we’re finally embracing fully Semantic Versioning, which should make the upgrade process simpler (painless?) for everyone. Going forward the following things will happen only on major releases:

  • enabling of new cops
  • changes to the default cop configuration
  • breaking API changes

This means that we should be able to update and safely lock new projects to the major instead of being limited in the minor. This means updating rules that may have changed their name before 1.0 and after 0.82 (version we are currently using) if needed and take a look at new rules enabled in the same time frame.

This should update potassium as well as projects generated with it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

1 participant