Skip to content

Refactor release process: attaching artifacts #2995

Closed

Description

@jsjoeio

The current release process feels brittle (from a maintainer's POV). We should improve it in terms of attaching artifacts to a release.

Issue created as suggestion action from regression report

Activity

  1. added this to the On Deck milestone on Mar 29, 2021
  2. added
    choreRelated to maintenance or clean up
    on May 14, 2021
  3. jsjoeio commented on Sep 15, 2021

    @jsjoeio
    ContributorAuthor

    We should def switch to building the release off the tag or something
    Then we can just tag a point where we want a release and done

    — @code-asher

  4. modified the milestones: On Deck, 3.12.1 on Sep 15, 2021
  5. stale commented on May 1, 2022

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no activity occurs in the next 5 days.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    choreRelated to maintenance or clean upciIssues related to ci

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions