Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: automate release workflow #2325

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Commits on Feb 21, 2024

  1. chore: lint README.md

    To primarily avoid conflicts and allow for automations.
    
    Signed-off-by: Pranshu Srivastava <rexagod@gmail.com>
    rexagod committed Feb 21, 2024
    Configuration menu
    Copy the full SHA
    a3a277d View commit details
    Browse the repository at this point in the history
  2. Update VERSION to reflect the latest patch release

    Reflect patch release changes on main, which was not the case with
    2.10.1 since that diverged and was never merged back into main (around
    backporting concerns).
    
    I believe in the future we can merge everything
    back into main to reflect the latest version changes in main, but
    diverge the release branches starting from the pre-merge commit to make
    sure backports are clean and maintainable (these will not be merged back
    into the default branch).
    
    Signed-off-by: Pranshu Srivastava <rexagod@gmail.com>
    rexagod committed Feb 21, 2024
    Configuration menu
    Copy the full SHA
    e1ef74e View commit details
    Browse the repository at this point in the history

Commits on Mar 5, 2024

  1. chore: automate release workflow

    Signed-off-by: Pranshu Srivastava <rexagod@gmail.com>
    rexagod committed Mar 5, 2024
    Configuration menu
    Copy the full SHA
    26e02a6 View commit details
    Browse the repository at this point in the history