Publish script fails in the last step despite the new versions are released

[Javier Toledo]

Bug Report

Current Behavior

The script fails in the last command of the "Publish using Rush" step while updating the main branch as can be seen here:

* EXECUTING: /usr/bin/git push origin HEAD:origin/main --follow-tags --verbose 
Pushing to https://github.com/boostercloud/booster.git
#############################################
#                                           #
#  ⚠️  Remember to execute `rush lint:fix` ⚠️ #
#                                           #
#############################################
POST git-receive-pack (2922 bytes)
To https://github.com/boostercloud/booster.git
 * [new tag]           @boostercloud/application-tester_v1.0.2 -> @boostercloud/application-tester_v1.0.2
 * [new tag]           @boostercloud/cli_v1.0.2 -> @boostercloud/cli_v1.0.2
 * [new tag]           @boostercloud/framework-common-helpers_v1.0.2 -> @boostercloud/framework-common-helpers_v1.0.2
 * [new tag]           @boostercloud/framework-core_v1.0.2 -> @boostercloud/framework-core_v1.0.2
 * [new tag]           @boostercloud/framework-provider-aws-infrastructure_v1.0.2 -> @boostercloud/framework-provider-aws-infrastructure_v1.0.2
 * [new tag]           @boostercloud/framework-provider-aws_v1.0.2 -> @boostercloud/framework-provider-aws_v1.0.2
 * [new tag]           @boostercloud/framework-provider-azure-infrastructure_v1.0.2 -> @boostercloud/framework-provider-azure-infrastructure_v1.0.2
 * [new tag]           @boostercloud/framework-provider-azure_v1.0.2 -> @boostercloud/framework-provider-azure_v1.0.2
 * [new tag]           @boostercloud/framework-provider-kubernetes-infrastructure_v1.0.2 -> @boostercloud/framework-provider-kubernetes-infrastructure_v1.0.2
 * [new tag]           @boostercloud/framework-provider-kubernetes_v1.0.2 -> @boostercloud/framework-provider-kubernetes_v1.0.2
 * [new tag]           @boostercloud/framework-provider-local-infrastructure_v1.0.2 -> @boostercloud/framework-provider-local-infrastructure_v1.0.2
 * [new tag]           @boostercloud/framework-provider-local_v1.0.2 -> @boostercloud/framework-provider-local_v1.0.2
 * [new tag]           @boostercloud/framework-types_v1.0.2 -> @boostercloud/framework-types_v1.0.2
 * [new tag]           @boostercloud/metadata-booster_v1.0.2 -> @boostercloud/metadata-booster_v1.0.2
 ! [rejected]          HEAD -> origin/main (non-fast-forward)
error: failed to push some refs to 'https://github.com/boostercloud/booster.git'
hint: Updates were rejected because a pushed branch tip is behind its remote
hint: counterpart. Check out this branch and integrate the remote changes
hint: (e.g. 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

ERROR: The command failed with exit code 1

Error: Process completed with exit code 1.

Possible Solution

Doing a pull before running this command could solve the issue. I.e. adding a step that does:

git pull --rebase origin/main

[Nick Seagull]

Working on it right now