What are the next steps after i build a release of my addon (based on cookieplone project layout)
That is what I've done so far
cd ./backend
pipx install hatch
hatch build
now in ./backend/dist/ live the addon.whl and addon.tar.gz
In the old way i use fullrelease from the zest.releaser package, with towncrier and zest.pocompile .
What is the new way to increment the version number and to build the changelog in the cookieplone based project?
@stevepiercy Update
I continue to use zest.releaser. it works. but i'm a little bit confused with the version tag in the cookieplone project layout. at the end of the day i break the single layout directory for frontend and backend in two seperate projects. i need gitlab support and build my own docker containers. i don't use the defaults of cookieplone.
Update
I only can use zest.releaser in the backend addon with modification of pyproject.toml
I have a related question about monorepo releases.
I’ve noticed that there are release scripts in both the backend and frontend Makefiles, but each of them creates its own tag (fullrelease and pnpm release). As a result, I end up with two different tags for each release, which is not what I want for a monorepo package.
I’ve looked at volto-contact-block as an example: it creates a single release tag for both frontend and backend, but I can’t figure out where that tag is actually created.
Does anyone have any suggestions or ideas? @ericof ?