🚀🧑‍💻 - 1.0.21 - New Release

[efraespada]

Release Type

Patch

Release Version

Automatic

Changelog

Test deploy actions.

Additional Context

Good luck!

[github-actions]

🪄 Automatic Actions

1. The issue was assigned to @efraespada (creator).
2. The issue was linked to Landa Messenger Development.
3. The issue's title was updated from <YOUR TITLE HERE> to 🚀🧑‍💻 - 1.0.21.
4. The branch develop was used to create the branch release/1.0.21

Reminder

1. Make yourself a coffee ☕.
2. Before deploying, apply any change needed in release/1.0.21.

Version files, changelogs, last minute changes.

3. Before deploying, create the tag version release/1.0.21.

Avoid using git merge --squash, otherwise the created tag will be lost.

4. Add the deploy label to run the release_workflow.yml workflow.
5. After deploying, the new changes on release/1.0.21 must end on develop and master.

Quick actions:
New PR from release/1.0.21 to develop.
New PR from release/1.0.21 to master.

Thank you for contributing! 🙌

[github-actions]

🪄 Automatic Actions

1. The issue's title was updated from 🚀🧑‍💻 - 1.0.21 to 🚀🧑‍💻 - 1.0.21.
2. Executed release workflow release_workflow.yml on release/1.0.21.

Workflow Parameters

{
    "version": "1.0.21",
    "title": "Demo Release Title",
    "changelog": "Demo changelog",
    "issue": "79"
}

Reminder

1. Make yourself a coffee ☕.
2. After deploying, the new changes on release/1.0.21 must end on develop and master.

Quick actions:
New PR from release/1.0.21 to develop.
New PR from release/1.0.21 to master.

Thank you for contributing! 🙌

[github-actions]

🚀 Release Actions

1. The issue's title was updated from New Release to 🚀🧑‍💻 - 1.0.21 - New Release.

Reminder

1. Make yourself a coffee ☕.
2. After deploying, the new changes on release/1.0.21 must end on develop and master.

Quick actions:
New PR from release/1.0.21 to develop.
New PR from release/1.0.21 to master.

Thank you for contributing! 🙌