Improvement/hd 4608 fix release workflow

[benzekrimaha]

Issue: HD-4608

[bert-e]

Hello benzekrimaha,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

[SylvainSenechal]

can update checkout to v6 and setup node to v6 if you want

[SylvainSenechal]

whats that, If the branch isn't main, publish npm will not be run ? Doesn't it means that when releasing from developemnt/x, it will be blocked since its not main 🤔

[maeldonn]

Suggested change

	if: github.ref == 'refs/heads/main'
	if: startsWith(github.ref, 'refs/heads/development/')

[maeldonn]

Same review as Sylvain. If we only run the workflow on development/ branches, we can get rid of the extra checks.

on:
    workflow_dispatch:
      inputs:
        tag:
          description: 'Tag to be released'
          required: true
      branches:
        - 'development/**'

[maeldonn]

Suggested change

	if: github.ref == 'refs/heads/main'
	if: startsWith(github.ref, 'refs/heads/development/')

[benzekrimaha]

/approve

[bert-e]

Integration data created

I have created the integration data for the additional destination branches.

• this pull request will merge improvement/HD-4608-fix-release-workflow into
  development/1.3
• w/1/improvement/HD-4608-fix-release-workflow will be merged into development/1

The following branches will NOT be impacted:

• development/1.0
• development/1.1
• development/1.2

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/1.3

• ✔️ development/1

The following branches have NOT changed:

• development/1.0
• development/1.1
• development/1.2

Please check the status of the associated issue HD-4608.

Goodbye benzekrimaha.

The following options are set: approve