We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After discussion in this thread bout version in migrations https://a8c.slack.com/archives/CK365S85V/p1649061443268359 @JPry built a mod for Woo Release in order to replace the x.x.x string in the Migration classes.
x.x.x
We need to handle manually DB Migration version changes
Implement the mod built by @JPry in the Grow toolset in a way could be easily used by the team
Implement it directly in WR repo
It'd be the first composer package.
The developer still needs to remember to execute this when doing the release so maybe it's possible to detect this in a more automatic way?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
After discussion in this thread bout version in migrations https://a8c.slack.com/archives/CK365S85V/p1649061443268359 @JPry built a mod for Woo Release in order to replace the
x.x.x
string in the Migration classes.Is your feature request related to a problem?
We need to handle manually DB Migration version changes
Describe the solution you'd like
Implement the mod built by @JPry in the Grow toolset in a way could be easily used by the team
Describe alternatives you've considered
Implement it directly in WR repo
Technical
It'd be the first composer package.
Acceptance criteria
Unknowns
The developer still needs to remember to execute this when doing the release so maybe it's possible to detect this in a more automatic way?
The text was updated successfully, but these errors were encountered: