Closed kingdonb closed 1 year ago
You can't just update config/version.yml
– it's baked from lib/templates/version.yml.erb
which is intended to be managed by some CI process, I think. Ideally we have rake app:version:bump
which takes a parameter like MINOR=true
and no human is managing these files.
We'll have to make this better with release scaffolding later, so I think it's OK to hold off on writing RELEASING.md
for now.
Fix #27
This release also introduces a convention, in the Production overlay (
deploy/overlays/production/
) wherein we're keeping the current release's version number:In addition to
config/version.yml
, we should update the version here. It may be time to createRELEASING.md
and centralize this information, whatever knowledge is needed to push a new version.The other necessary information that was added recently, a version setting in
version.yml
must be in sync with the version in the Git tag, else the release process will abort and fail (having published no release artifacts, other than the tag itself.)I'm using a gem called
app_version
to help manage this, it doesn't seem to be maintained, but I think that's probably OK.