i moved mariadb to another compose file enabled by default hoping it won't break during upgrades, but i don't remember if updating the env file is part of the upgrade process :B
i moved mariadb to another compose file enabled by default hoping it won't break during upgrades, but i don't remember if updating the env file is part of the upgrade process :B
Looks good! If we wanted to be super organised we could add a release note alerting people to the need to update their .envs, indeed it is not automatic 😬
Looks good! If we wanted to be super organised we could add a release note alerting people to the need to update their `.env`s, indeed it is not automatic 😬
Looks good, but it will break the update, people need to change the env file manually. (Only Alakazam is updating the env files automatically)
This should be a major release and it needs a note in the release notes.
Looks good, but it will break the update, people need to change the env file manually. (Only Alakazam is updating the env files automatically)
This should be a major release and it needs a note in the release notes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
i moved mariadb to another compose file enabled by default hoping it won't break during upgrades, but i don't remember if updating the env file is part of the upgrade process :B
Looks good! If we wanted to be super organised we could add a release note alerting people to the need to update their
.envs, indeed it is not automatic 😬LGTM.
(Release note would be good indeed!)
i'd like @moritz opinion on this!
Looks good, but it will break the update, people need to change the env file manually. (Only Alakazam is updating the env files automatically)
This should be a major release and it needs a note in the release notes.
thanks! i see... i'm okay with a major release + release note then. the rest is a case for toolshed/abra#504
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.