Skip to content

πŸš€πŸ§‘β€πŸ’» - 1.0.46 - Improving LogsΒ #199

Closed

Description

@efraespada

Release Type

Patch

Release Version

Automatic

Changelog

  • Improving logs
  • Fixed AI ignoring files

Additional Context

No response

Activity

  1. changed the title [-]Improving Logs[/-] [+]πŸš€πŸ§‘β€πŸ’» - 1.0.46 - Improving Logs[/+] on Mar 25, 2025
  2. github-actions commented on Mar 25, 2025

    @github-actions
    Contributor

    πŸš€ Release 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 Improving Logs to πŸš€πŸ§‘β€πŸ’» - 1.0.46 - Improving Logs.
    4. The branch develop was used to create the branch release/1.0.46

    image

    Reminder

    1. Take a coffee break while you work β˜•.
    2. Before deploying, apply any change needed in release/1.0.46:
    git fetch -v && git checkout release/1.0.46

    Version files, changelogs..

    1. Commit the needed changes with this prefix:
    release-1.0.46
    
    1. Create the tag version in release/1.0.46.

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

    1. Add the deploy label to run the release_workflow.yml workflow.
    2. After deploying, the new changes on release/1.0.46 must end on develop and master.

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

    πŸš€ Happy coding!

  3. github-actions commented on Mar 25, 2025

    @github-actions
    Contributor

    πŸš€ Release Actions

    1. The issue's title was updated from Improving Logs to πŸš€πŸ§‘β€πŸ’» - 1.0.46 - Improving Logs.
    2. Executed release workflow release_workflow.yml on release/1.0.46.

    Workflow Parameters

    {
        "version": "1.0.46",
        "title": "Improving Logs",
        "changelog": "- Improving logs\\n- Fixed AI ignoring files",
        "issue": "199"
    }

    image

    Reminder

    1. Take a coffee break while you work β˜•.
    2. After deploying, the new changes on release/1.0.46 must end on develop and master.

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

    πŸš€ Happy coding!

  4. linked a pull request that will close this issueMerge release/1.0.46 into master #200on Mar 25, 2025
  5. github-actions commented on Mar 25, 2025

    @github-actions
    Contributor

    πŸš€ Release Actions

    1. Label deployed added after a success deploy.
    2. The branch release/1.0.46 was merged into master.
    3. The branch release/1.0.46 was merged into develop.

    image

    πŸš€ Happy coding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

branchedIndicates that a branch has been created for this issue.deployedrelease

Type

No type

Projects

  • Status
    Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions