Skip to content

Release: v1.1.2 #17

@zoidy

Description

@zoidy

Name the Issue

  • I have named this issue using the new version number.

Steps

  • Check that the title of this issue reflects the new version number.
  • Create a new branch by clicking on create branch on the right-hand sidebar (as shown in the GitHub docs). Leave all options as default.
  • In the new branch, update the version in Code.gs and version.py as needed. The overall version of the release may diverge from the versions in the two files (e.g., release version 2.0.0 may correspond to v1.1. of the WebApp and v2.0 of the reports code. Commit the changes.
  • Create a new PR. Ensure the base branch is main and the comparison branch is the new branch. Use the "Release" PR template.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions