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

Chore: Bump to Shakapacker v7 #3946

Closed
2 tasks
KevinMulhern opened this issue Jul 10, 2023 · 2 comments
Closed
2 tasks

Chore: Bump to Shakapacker v7 #3946

KevinMulhern opened this issue Jul 10, 2023 · 2 comments
Labels
Type: Chore Involves changes with no user-facing value, to the build process/internal tooling, refactors, etc.

Comments

@KevinMulhern
Copy link
Member

1. Description of the Feature Request:
A new major version of Shakapacker just dropped.

2. Acceptance Criteria:

  • CI passes with Shakapacker v7
  • Review app builds with Shakapacker v7
@KevinMulhern KevinMulhern added the Type: Chore Involves changes with no user-facing value, to the build process/internal tooling, refactors, etc. label Jul 10, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog / Ideas in Main Site Jul 10, 2023
@KevinMulhern KevinMulhern moved this from 📋 Backlog / Ideas to 🔖 Ready for Development in Main Site Jul 10, 2023
@KevinMulhern KevinMulhern mentioned this issue Jul 10, 2023
Closed
@ahasunos
Copy link

I could help with this issue.

@ahasunos
Copy link

However, we have the latest version of Shakapacker here as 7.1.0 https://rubygems.org/gems/shakapacker/versions/7.1.0

@github-project-automation github-project-automation bot moved this from 🔖 Ready for Development to ✅ Done in Main Site Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type: Chore Involves changes with no user-facing value, to the build process/internal tooling, refactors, etc.
Projects
Main Site
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@KevinMulhern @ahasunos