Closed will-moore closed 4 years ago
Thanks. Merging. @will-moore do you want to drive and cut a patch release of omero-gallery
and open a PR against https://github.com/IDR/deployment/blob/6d367a3820a2915095888ea8434aa192f791a654/ansible/group_vars/omero-hosts.yml#L215 to consume it in the next IDR release? What about the open dependency PRs?
OK, so I remove the .dev from version as in https://github.com/ome/omero-gallery/commit/83044dc8820871d96f07dceff401763fd6bcdefd Then push a Tag for v3.3.3, then... It doesn't look like that would push a release to Pypi automatically?? Then another commit to add back 'dev' to versions.
This might be worth a dedicated Release
section in the top-level README. As far as I know, the current release process is identical to omero-py
and omero-web
i.e.:
bumpversion release
to remove the dev suffix and create a signed tagbumpversion --no-tag patch
to bump the version to the next dev suffixmaster
to origin
Hmm - I need some more setting up before I try this:
$ bumpversion release
error: cannot run gpg: No such file or directory
error: gpg failed to sign the data
error: unable to sign the tag
Creating signed Git tags requires gpg
installed and your private GPG key configured. You might as well want to upload your public key to GitHub - https://docs.github.com/en/github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account
Done: $ git push origin master v3.3.3
This tweaks the css for categories page to fix the Titles and image panels expanding outside the screen:
To test:
Before: