rubygems publishing by tagging?

[opoudjis]

I've started using tags instead of rake release to push out versions of gems. I've manually pushed mn-requirements to rubygems, since neither 0.0.3 nor 0.1.0 was pushed (the former 5 days ago). Could I confirm that tagging is set up to publish mn-requirements ?

[ronaldtse]

For starters, you need to run these commands to grant publication privileges.

gem owner mn-requirements -a ribose
gem owner mn-requirements -a metanorma

[CAMOBAP]

Because we use general workflow for many repositories, some of them require access to GH rubygems.
@ronaldtse could you please confirm that this repo has access to both:

• secrets.METANORMA_CI_RUBYGEMS_API_KEY
• secrets.METANORMA_CI_PAT_TOKEN

*both are org-level secrets as far as I remember

[ronaldtse]

@CAMOBAP yes they are both available here, it is only with private repos we have to manually set. The issue is that @opoudjis needs to add the CI user as gem owner.

[opoudjis]

Done.

[ronaldtse]

Confirm done.

[CAMOBAP]

@ronaldtse @opoudjis should we rerun latest failed release workflow?

[opoudjis]

Btw, Github Actions is going to fail for all of mn-requirements, metanorma-standoc and isodoc, because of circular dependencies: they all need to be upgraded together.

[CAMOBAP]

@opoudjis https://github.com/metanorma/metanorma-standoc/tree/main/.github/workflows doesn't have automatic release workflow as many other gems, I tried to add release workflow to only independent components

Anyway let me know if there is make sense to add/remove automatic release workflow for some repos

[ronaldtse]

@CAMOBAP we want automatic release for all gems in the metanorma, relaton orgs. Thanks!

[CAMOBAP]

@CAMOBAP we want automatic release for all gems in the metanorma, relaton orgs. Thanks!

Ok

cc @andrew2net to be on the same page. AFAIK you are probably working on relaton projects more than others

Btw, Github Actions is going to fail for all of mn-requirements, metanorma-standoc and isodoc, because of circular dependencies: they all need to be upgraded together.

This "circle" comes from development deps, to me, it looks like the order should be:

• mn-requirements
• isodoc
• metanorma-standoc

will it works?

[CAMOBAP]

@ronaldtse could you please confirm that RELATON_CI_RUBYGEMS_API_KEY or similar is available for relaton org?

UPD. Just found that RELATON_CI_RUBYGEMS_API_KEY exists at least in relaton-cli I hope it defined on org level

@andrew2net just for you to know CI now will do push to rubygems once you did tag on the repo, in case of any issues don't hesitate to contact me

I'm going to add the same for all metanorma gems, probably I will create individual PR so we will be able to check each case individually to discuss possible circular deps or other potential problems

[CAMOBAP]

CI configuration updated for all rmetanorma and relaton epos

[andrew2net]

@CAMOBAP I've tried to make tag and push it to relaton-bipm repo but nothing happened.

error parsing called workflow "relaton/support/.github/workflows/release.yml@master": failed to fetch workflow: workflow was not found.

https://github.com/relaton/relaton-bipm/actions/runs/3028659644

[CAMOBAP]

@andrew2net my bad forgot to push relaton/support could you please try one more time

Update: I just executed the release manually https://github.com/relaton/relaton-bipm/actions/workflows/release.yml (with skip option) to check if it works. It pass all steps just failed on rubygem.org push because this version already exists. so I tink now it works properly

[andrew2net]

@CAMOBAP I've already released the relaton-bipm using rake release command. Will try next time.

[andrew2net]

@CAMOBAP what is correct workflow to release gem?
I make a commit, then I push the commit and wait until all GHA tests completed, then create a tag and push it.
Then I push tag the GHA tests run again. I think we don't need it.

[CAMOBAP]

Then I push tag the GHA tests run again. I think we don't need it.

Agree, we have workaround for this on metanorma gems, I will implement the same approach for relaton gems

[CAMOBAP]

@andrew2net done relaton/support@e24abac