[med-svn] [Git][med-team/conda-package-handling][upstream] New upstream version 2.2.0

Andreas Tille (@tille) gitlab at salsa.debian.org
Mon Sep 11 11:33:40 BST 2023



Andreas Tille pushed to branch upstream at Debian Med / conda-package-handling


Commits:
9c76bb45 by Andreas Tille at 2023-09-11T12:29:19+02:00
New upstream version 2.2.0
- - - - -


21 changed files:

- .authors.yml
- .github/ISSUE_TEMPLATE/0_bug.yml
- .github/ISSUE_TEMPLATE/1_feature.yml
- .github/ISSUE_TEMPLATE/epic.yml
- .github/workflows/cla.yml
- .github/workflows/issues.yml
- .github/workflows/labels.yml
- .github/workflows/lock.yml
- .github/workflows/project.yml
- .github/workflows/stale.yml
- .pre-commit-config.yaml
- CHANGELOG.md
- HOW_WE_USE_GITHUB.md
- README.md
- RELEASE.md
- conda.recipe/meta.yaml
- docs/requirements.txt
- rever.xsh
- + rever_overrides.xsh
- setup.py
- src/conda_package_handling/__init__.py


Changes:

=====================================
.authors.yml
=====================================
@@ -61,7 +61,7 @@
   github: dbast
 - name: Conda Bot
   email: 18747875+conda-bot at users.noreply.github.com
-  num_commits: 17
+  num_commits: 23
   first_commit: 2022-01-17 20:22:29
   github: conda-bot
   aliases:
@@ -86,7 +86,7 @@
   first_commit: 2022-02-17 10:23:53
 - name: Daniel Holth
   email: dholth at anaconda.com
-  num_commits: 21
+  num_commits: 24
   first_commit: 2021-08-20 21:11:50
   github: dholth
 - name: Vadim Zayakin
@@ -122,5 +122,5 @@
 - name: pre-commit-ci[bot]
   email: 66853113+pre-commit-ci[bot]@users.noreply.github.com
   github: pre-commit-ci[bot]
-  num_commits: 4
+  num_commits: 7
   first_commit: 2023-01-20 04:55:56


=====================================
.github/ISSUE_TEMPLATE/0_bug.yml
=====================================
@@ -1,3 +1,4 @@
+---
 name: Bug Report
 description: Create a bug report.
 labels:


=====================================
.github/ISSUE_TEMPLATE/1_feature.yml
=====================================
@@ -1,3 +1,4 @@
+---
 name: Feature Request
 description: Create a feature request.
 labels:


=====================================
.github/ISSUE_TEMPLATE/epic.yml
=====================================
@@ -1,3 +1,4 @@
+---
 name: Epic
 description: A collection of related tickets.
 labels:


=====================================
.github/workflows/cla.yml
=====================================
@@ -1,3 +1,4 @@
+---
 name: CLA
 
 on:
@@ -5,27 +6,31 @@ on:
     types:
       - created
   pull_request_target:
-    types:
-      - reopened
-      - opened
-      - synchronize
 
 jobs:
   check:
     if: >-
       !github.event.repository.fork
       && (
-        github.event.comment.body == '@conda-bot check'
+        github.event.issue.pull_request
+        && github.event.comment.body == '@conda-bot check'
         || github.event_name == 'pull_request_target'
       )
     runs-on: ubuntu-latest
     steps:
       - name: Check CLA
-        uses: conda/actions/check-cla at v22.9.0
+        uses: conda/actions/check-cla at v23.7.0
         with:
           # [required]
-          # label to add when actor has signed the CLA
+          # A token with ability to comment, label, and modify the commit status
+          # (`pull_request: write` and `statuses: write` for fine-grained PAT; `repo` for classic PAT)
+          # (default: secrets.GITHUB_TOKEN)
+          token: ${{ secrets.CLA_ACTION_TOKEN }}
+          # [required]
+          # Label to apply to contributor's PR once CLA is singed
           label: cla-signed
+
           # [required]
-          # the GitHub Personal Access Token to comment and label with
-          token: "${{ secrets.CLA_ACTION_TOKEN }}"
+          # Token for opening singee PR in the provided `cla_repo`
+          # (`pull_request: write` for fine-grained PAT; `repo` and `workflow` for classic PAT)
+          cla_token: ${{ secrets.CLA_FORK_TOKEN }}


=====================================
.github/workflows/issues.yml
=====================================
@@ -1,3 +1,4 @@
+---
 name: Automate Issues
 
 on:


=====================================
.github/workflows/labels.yml
=====================================
@@ -1,3 +1,4 @@
+---
 name: Sync Labels
 
 on:
@@ -6,7 +7,7 @@ on:
   workflow_dispatch:
     inputs:
       dryrun:
-        description: "dryrun: Preview changes to labels without editing them (true|false)"
+        description: 'dryrun: Preview changes to labels without editing them (true|false)'
         required: true
         type: boolean
         default: true


=====================================
.github/workflows/lock.yml
=====================================
@@ -1,3 +1,4 @@
+---
 name: Lock
 
 on:
@@ -26,9 +27,9 @@ jobs:
           # Do not lock issues with these labels, value must be a comma separated list of labels or ''
           exclude-any-issue-labels: ''
           # Labels to add before locking an issue, value must be a comma separated list of labels or ''
-          add-issue-labels: 'locked'
+          add-issue-labels: locked
           # Reason for locking an issue, value must be one of resolved, off-topic, too heated, spam or ''
-          issue-lock-reason: 'resolved'
+          issue-lock-reason: resolved
 
           # Number of days of inactivity before a closed pull request is locked
           pr-inactive-days: 365
@@ -37,9 +38,9 @@ jobs:
           # Do not lock pull requests with these labels, value must be a comma separated list of labels or ''
           exclude-any-pr-labels: ''
           # Labels to add before locking a pull request, value must be a comma separated list of labels or ''
-          add-pr-labels: 'locked'
+          add-pr-labels: locked
           # Reason for locking a pull request, value must be one of resolved, off-topic, too heated, spam or ''
-          pr-lock-reason: 'resolved'
+          pr-lock-reason: resolved
 
           # Limit locking to only issues or pull requests, value must be one of issues, prs or ''
           process-only: ''


=====================================
.github/workflows/project.yml
=====================================
@@ -1,3 +1,4 @@
+---
 name: Add to Project
 
 on:
@@ -13,7 +14,7 @@ jobs:
     if: '!github.event.repository.fork'
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/add-to-project at v0.4.1
+      - uses: actions/add-to-project at v0.5.0
         with:
           # issues are added to the Planning project
           # PRs are added to the Review project


=====================================
.github/workflows/stale.yml
=====================================
@@ -1,3 +1,4 @@
+---
 name: Stale
 
 on:
@@ -6,7 +7,7 @@ on:
   workflow_dispatch:
     inputs:
       dryrun:
-        description: "dryrun: Preview stale issues/prs without marking them (true|false)"
+        description: 'dryrun: Preview stale issues/prs without marking them (true|false)'
         required: true
         type: boolean
         default: true
@@ -30,15 +31,15 @@ jobs:
             days-before-issue-close: 30
           # [type::support] issues have a more aggressive stale/close timeline
           - only-issue-labels: type::support
-            days-before-issue-stale: 21
-            days-before-issue-close: 7
+            days-before-issue-stale: 90
+            days-before-issue-close: 21
     steps:
-      - uses: conda/actions/read-yaml at v22.9.0
+      - uses: conda/actions/read-yaml at v23.7.0
         id: read_yaml
         with:
           path: https://raw.githubusercontent.com/conda/infra/main/.github/messages.yml
 
-      - uses: actions/stale at v7
+      - uses: actions/stale at v8
         id: stale
         with:
           # Only issues with these labels are checked whether they are stale
@@ -68,8 +69,6 @@ jobs:
           stale-pr-label: stale
           # Label to apply on closed PRs
           close-pr-label: stale::closed
-          # Reason to use when closing PRs
-          close-pr-reason: not_planned
 
           # Remove stale label from issues/PRs on updates/comments
           remove-stale-when-updated: true


=====================================
.pre-commit-config.yaml
=====================================
@@ -16,7 +16,7 @@ repos:
       # catch git merge/rebase problems
       - id: check-merge-conflict
   - repo: https://github.com/asottile/pyupgrade
-    rev: v3.3.2
+    rev: v3.9.0
     hooks:
       - id: pyupgrade
         args: ["--py37-plus"]
@@ -25,7 +25,7 @@ repos:
     hooks:
     -   id: isort
   - repo: https://github.com/psf/black
-    rev: 23.3.0
+    rev: 23.7.0
     hooks:
     -   id: black
   - repo: https://github.com/PyCQA/flake8


=====================================
CHANGELOG.md
=====================================
@@ -1,5 +1,24 @@
 [//]: # (current developments)
 
+## 2.2.0 (2023-07-28)
+
+### Bug fixes
+
+* Respect umask when unpacking packages, by requiring `conda-package-streaming >= 0.9.0`.
+
+### Docs
+
+* Include README.md in pypi metadata. (#215)
+
+### Contributors
+
+* @conda-bot
+* @dbast
+* @dholth
+* @pre-commit-ci[bot]
+
+
+
 ## 2.1.0 (2023-05-04)
 
 ### Bug fixes


=====================================
HOW_WE_USE_GITHUB.md
=====================================
@@ -11,40 +11,47 @@
 [docs-toc]: https://github.blog/changelog/2021-04-13-table-of-contents-support-in-markdown-files/
 [docs-actions]: https://docs.github.com/en/actions
 [docs-saved-reply]: https://docs.github.com/en/get-started/writing-on-github/working-with-saved-replies/creating-a-saved-reply
+[docs-commit-signing]: https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits
 
-[workflow-sync]: https://github.com/conda/infra/blob/main/.github/workflows/sync.yml
-[labels-global]: https://github.com/conda/infra/blob/main/.github/global.yml
-
-[signing-commits]: https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits
+[infrastructure]: https://github.com/conda/infrastructure
+[workflow-sync]: https://github.com/conda/infrastructure/blob/main/.github/workflows/sync.yml
+[labels-global]: https://github.com/conda/infrastructure/blob/main/.github/global.yml
 
 <!-- relative URLs -->
+[workflow-cla]: /.github/workflows/cla.yml
 [workflow-issues]: /.github/workflows/issues.yml
+[workflow-labels]: /.github/workflows/labels.yml
+[workflow-lock]: /.github/workflows/lock.yml
 [workflow-project]: /.github/workflows/project.yml
+[workflow-stale]: /.github/workflows/stale.yml
 [labels-local]: /.github/labels.yml
+[labels-page]: ../../labels
 
-## How We Use GitHub
-
-> **Note**
-> For easy navigation use [GitHub's table of contents feature][docs-toc].
+# How We Use GitHub
 
-This document seeks to outline how we as a community use GitHub Issues to track bugs and feature requests while still catering to development practices & project management (*e.g.*, release cycles, feature planning, priority sorting, etc.).
+This document seeks to outline how we as a community use GitHub Issues to track bugs and feature requests while still catering to development practices & project management (_e.g._, release cycles, feature planning, priority sorting, etc.).
 
 <!-- only include high-level topics or particularly noteworthy sections here -->
-Topics:
-  - [What is Issue Sorting?](#what-is-issue-sorting)
-  - [Commit signing](#commit-signing)
-  - [Types of tickets](#types-of-tickets)
-    - [Normal Ticket/Issue](#normal-ticketissue)
+**Topics:**
+
+  - [What is "Issue Sorting"?](#what-is-issue-sorting)
+  - [Issue Sorting Procedures](#issue-sorting-procedures)
+  - [Commit Signing](#commit-signing)
+  - [Types of Issues](#types-of-issues)
+    - [Standard Issue](#standard-issue)
     - [Epics](#epics)
     - [Spikes](#spikes)
+  - [Working on Issues](#working-on-issues)
 
+> **Note**
+> This document is written in the style of an FAQ. For easier navigation, use [GitHub's table of contents feature][docs-toc].
 
-### What is "Issue Sorting"?
+## What is "Issue Sorting"?
 
 > **Note**
-> "Issue sorting" is similar to that of "triaging", but we've chosen to use different terminology because "triaging" is a word related to very weighty topics (*e.g.*, injuries and war) and we would like to be sensitive to those connotations. Additionally, we are taking a more "fuzzy" approach to sorting (*e.g.*, severities may not be assigned, etc.).
+> "Issue sorting" is similar to that of "triaging", but we've chosen to use different terminology because "triaging" is a word related to very weighty topics (_e.g._, injuries and war) and we would like to be sensitive to those connotations. Additionally, we are taking a more "fuzzy" approach to sorting (_e.g._, severities may not be assigned, etc.).
 
-"Issue Sorting" refers to the process of assessing the priority of incoming issues. Below is a high-level diagram of the flow of tickets:
+"Issue Sorting" refers to the process of assessing the priority of incoming issues. Below is a high-level diagram of the flow of issues:
 
 ```mermaid
 flowchart LR
@@ -77,10 +84,7 @@ flowchart LR
     board_progress-- resolved -->state_closed
 ```
 
-In order to explain how various `conda` issues are evaluated, the following document will provide information about our sorting process in the form of an FAQ.
-
-
-#### Why sort issues?
+### Why sort issues?
 
 At the most basic "bird's eye view" level, sorted issues will fall into the category of four main priority levels:
 
@@ -91,104 +95,133 @@ At the most basic "bird's eye view" level, sorted issues will fall into the cate
 
 At its core, sorting enables new issues to be placed into these four categories, which helps to ensure that they will be processed at a velocity similar to or exceeding the rate at which new issues are coming in. One of the benefits of actively sorting issues is to avoid engineer burnout and to make necessary work sustainable; this is done by eliminating a never-ending backlog that has not been reviewed by any maintainers.
 
-There will always be broad-scope design and architecture implementations that the `conda` maintainers will be interested in pursuing; by actively organizing issues, the sorting engineers will be able to more easily track and tackle both specific and big-picture goals.
-
-#### Who does the sorting?
-
-Sorting engineers are a `conda` governance [sub-team][sub-team]; they are a group of Anaconda and community members who are responsible for making decisions regarding closing issues and setting feature work priorities, amongst other sorting-related tasks.
+There will always be broad-scope design and architecture implementations that the maintainers will be interested in pursuing; by actively organizing issues, the sorting engineers will be able to more easily track and tackle both specific and big-picture goals.
 
+### Who does the sorting?
 
-#### How do items show up for sorting?
+Sorting engineers are a conda governance [sub-team][sub-team]; they are a group of community members who are responsible for making decisions regarding closing issues and setting feature work priorities, among other sorting-related tasks.
 
-New issues that are opened in any of the repositories in the [`conda` GitHub project][conda-org] will show up in the `Sorting` view of the [Planning project][project-planning]. This process is executed via [GitHub Actions][docs-actions]. The two main GitHub Actions workflows utilized for this purpose are [Issues][workflow-issues] and [Project][workflow-project].
+### How do items show up for sorting?
 
-The GitHub Actions in the `conda/infra` repository are viewed as canonical; the [Sync workflow][workflow-sync] sends out any modifications to other `conda` repositories from there.
+New issues that are opened in any of the repositories in the [conda GitHub organization][conda-org] will show up in the "Sorting" tab of the [Planning project][project-planning]. There are two [GitHub Actions][docs-actions] workflows utilized for this purpose; [`.github/workflows/issues.yml`][workflow-issues] and [`.github/workflows/project.yml`][workflow-project].
 
+The GitHub Actions in the [`conda/infrastructure`][infrastructure] repository are viewed as canonical; the [`.github/workflows/sync.yml` workflow][workflow-sync] sends out any modifications to other `conda` repositories from there.
 
-#### What is done about the issues in "sorting" mode?
+### What is done about the issues in the "Sorting" tab?
 
-Issues in the ["Sorting" tab of the project board][project-sorting] have been reviewed by a sorting engineer and are considered ready for the following procedures:
+Issues in the ["Sorting" tab of the project board][project-sorting] are considered ready for the following procedures:
 
 - Mitigation via short-term workarounds and fixes
 - Redirection to the correct project
 - Determining if support can be provided for errors and questions
 - Closing out of any duplicate/off-topic issues
 
-The sorting engineers on rotation are not seeking to _resolve_ issues that arise. Instead, the goal is to understand the ticket and to determine whether it is an issue in the first place, and then to collect as much relevant information as possible so that the maintainers of `conda` can make an informed decision about the appropriate resolution schedule.
+The sorting engineers on rotation are not seeking to _resolve_ issues that arise. Instead, the goal is to understand the issue and to determine whether it is legitimate, and then to collect as much relevant information as possible so that the maintainers can make an informed decision about the appropriate resolution schedule.
 
-Issues will remain in the "Sorting" tab as long as the issue is in an investigatory phase (_e.g._, querying the user for more details, asking the user to attempt other workarounds, other debugging efforts, etc.) and are likely to remain in this state the longest, but should still be progressing over the course of 1-2 weeks.
+Issues will remain in the ["Sorting" tab][project-sorting] as long as the issue is in an investigatory phase (_e.g._, querying the user for more details, asking the user to attempt other workarounds, other debugging efforts, etc.) and are likely to remain in this state the longest, but should still be progressing over the course of 1-2 weeks.
 
+For more information on the sorting process, see [Issue Sorting Procedures](#issue-sorting-procedures).
 
-#### When do items move out of the "Sorting" tab?
+### When do items move out of the "Sorting" tab?
 
-The additional tabs in the project board that the issues can be moved to include the following:
+Items move out of the ["Sorting" tab][project-sorting] once the investigatory phase described in [What is done about the issues in the "Sorting" tab?](#what-is-done-about-the-issues-in-the-sorting-tab) has concluded and the sorting engineer has enough information to make a decision about the appropriate resolution schedule for the issue. The additional tabs in the project board that the issues can be moved to include the following:
 
-- **"Support"** - Any issue in the ["Support" tab of the Planning board][project-support] is a request for support and is not a feature request or a bug report. All issues considered "support" should include the https://github.com/conda/infra/labels/type%3A%3Asupport label.
-- **"Backlog"** - The issue has revealed a bug or feature request. We have collected enough details to understand the problem/request and to reproduce it on our own. These issues have been moved into the [Backlog tab of the Planning board][project-backlog] at the end of the sorting rotation during Refinement.
+- **"Support"** - Any issue in the ["Support" tab of the Planning board][project-support] is a request for support and is not a feature request or a bug report. Add the [`type::support`](https://github.com/conda/infrastructure/labels/type%3A%3Asupport) label to move an issue to this tab.
+- **"Backlog"** - The issue has revealed a bug or feature request. We have collected enough details to understand the problem/request and to reproduce it on our own. These issues have been moved into the [Backlog tab of the Planning board][project-backlog] at the end of the sorting rotation during Refinement. Add the [`backlog`](https://github.com/conda/infrastructure/labels/backlog) label to move an issue to this tab.
 - **"Closed"** - The issue was closed due to being a duplicate, being redirected to a different project, was a user error, a question that has been resolved, etc.
 
+### Where do work issues go after being sorted?
+
+Once issues are deemed ready to be worked on, they will be moved to the ["Backlog" tab of the Planning board][project-backlog]. Once actively in progress, the issues will be moved to the ["In Progress" tab of the Planning board][project-in-progress] and then closed out once the work is complete.
+
+### What is the purpose of having a "Backlog"?
 
-#### Where do items go after being sorted?
+Issues are "backlogged" when they have been sorted but not yet earmarked for an upcoming release.
 
-All sorted issues will be reviewed by sorting engineers during a weekly Refinement meeting in order to understand how those particular issues fit into the short- and long-term roadmap of `conda`. These meetings enable the sorting engineers to get together to collectively prioritize issues, earmark feature requests for specific future releases (versus a more open-ended backlog), tag issues as ideal for first-time contributors, as well as whether or not to close/reject specific feature requests.
+### What automation procedures are currently in place?
 
-Once issues are deemed ready to be worked on, they will be moved to the [`conda` Backlog tab of the Planning board][project-backlog] on GitHub. Once actively in progress, the issues will be moved to the [In Progress tab of the Planning board][project-in-progress] and then closed out once the work is complete.
+Global automation procedures synced out from the [`conda/infrastructure`][infrastructure] repo include:
 
+- [Marking of issues and pull requests as stale][workflow-stale], resulting in:
+  - issues marked as [`type::support`](https://github.com/conda/infrastructure/labels/type%3A%3Asupport) being labeled stale after 21 days of inactivity and being closed after 7 further days of inactivity (that is, closed after 30 inactive days total)
+  - all other inactive issues (not labeled as [`type::support`](https://github.com/conda/infrastructure/labels/type%3A%3Asupport) being labeled stale after 365 days of inactivity and being closed after 30 further days of inactivity (that is, closed after an approximate total of 1 year and 1 month of inactivity)
+  - all inactive pull requests being labeled stale after 365 days of inactivity and being closed after 30 further days of inactivity (that is, closed after an approximate total of 1 year and 1 month of inactivity)
+- [Locking of closed issues and pull requests with no further activity][workflow-lock] after 365 days
+- [Adding new issues and pull requests to the respective project boards][workflow-project]
+- [Indicating an issue is ready for the sorting engineer's attention][workflow-issues] by toggling [`pending::feedback`](https://github.com/conda/infrastructure/labels/pending%3A%3Afeedback) with [`pending::support`](https://github.com/conda/infrastructure/labels/pending%3A%3Asupport) after a contributor leaves a comment
+- [Verifying that contributors have signed the CLA][workflow-cla] before allowing pull requests to be merged; if the contributor hasn't signed the CLA previously, merging is be blocked until a manual review can be done
+- [Syncing out templates, labels, workflows, and documentation][workflow-sync] from [`conda/infrastructure`][infrastructure] to the other repositories
 
-#### What is the purpose of having a "Backlog"?
+## Issue Sorting Procedures
 
-Issues are "backlogged" when they have been sorted but not yet earmarked for an upcoming release. Weekly Refinement meetings are a time when the `conda` engineers will transition issues from "[Sorting][project-sorting]" to "[Backlog][project-backlog]". Additionally, this time of handoff will include discussions around the kind of issues that were raised, which provides an opportunity to identify any patterns that may point to a larger problem.
+### How are issues sorted?
 
+Issues in the ["Sorting" tab of the Planning board][project-sorting] are reviewed by issue sorting engineers, who take rotational sorting shifts. In the process of sorting issues, engineers label the issues and move them to the other tabs of the project board for further action.
 
-#### How does labeling work?
+Issues that require input from multiple members of the sorting team will be brought up during refinement meetings in order to understand how those particular issues fit into the short- and long-term roadmap. These meetings enable the sorting engineers to get together to collectively prioritize issues, earmark feature requests for specific future releases (versus a more open-ended backlog), tag issues as ideal for first-time contributors, as well as whether or not to close/reject specific feature requests.
+
+### How does labeling work?
 
 Labeling is a very important means for sorting engineers to keep track of the current state of an issue with regards to the asynchronous nature of communicating with users. Utilizing the proper labels helps to identify the severity of the issue as well as to quickly understand the current state of a discussion.
 
-Generally speaking, labels with the same category are considered mutually exclusive but in some cases labels sharing the same category can occur concurrently as they indicate qualifiers as opposed to types. For example, we may have the following types, https://github.com/conda/infra/labels/type%3A%3Abug, https://github.com/conda/infra/labels/type%3A%3Afeature, and https://github.com/conda/infra/labels/type%3A%3Adocumentation, where for any one issue there would be _at most_ **one** of these to be defined (_i.e._ an issue shouldn’t be a bug _and_ a feature request at the same time). Alternatively, with issues involving specific operating systems (_i.e._, https://github.com/conda/infra/labels/os%3A%3Alinux, https://github.com/conda/infra/labels/os%3A%3Amacos, and https://github.com/conda/infra/labels/os%3A%3Awindows), an issue could be labeled with one or more depending on the system(s) the issue is occurring on.
+Each label has an associated description that clarifies how the label should be used. Hover on the label to see its description. Label colors are used to distinguish labels by category.
+
+Generally speaking, labels with the same category are considered mutually exclusive, but in some cases labels sharing the same category can occur concurrently, as they indicate qualifiers as opposed to types. For example, we may have the following types, [`type::bug`](https://github.com/conda/infrastructure/labels/type%3A%3Abug), [`type::feature`](https://github.com/conda/infrastructure/labels/type%3A%3Afeature), and [`type::documentation`](https://github.com/conda/infrastructure/labels/type%3A%3Adocumentation), where for any one issue there would be _at most_ **one** of these to be defined (_i.e._ an issue should not be a bug _and_ a feature request at the same time). Alternatively, with issues involving specific operating systems (_i.e._, [`os::linux`](https://github.com/conda/infrastructure/labels/os%3A%3Alinux), [`os::macos`](https://github.com/conda/infrastructure/labels/os%3A%3Amacos), and [`os::windows`](https://github.com/conda/infrastructure/labels/os%3A%3Awindows)), an issue could be labeled with one or more, depending on the system(s) the issue occurs on.
+
+Please note that there are also automation policies in place that are affected by labeling. For example, if an issue is labeled as [`type::support`](https://github.com/conda/infrastructure/labels/type%3A%3Asupport), that issue will be marked [`stale`](https://github.com/conda/infrastructure/labels/stale) after 21 days of inactivity and auto-closed after seven more days without activity (30 inactive days total), which is earlier than issues without this label. See [What automation procedures are currently in place?](#what-automation-procedures-are-currently-in-place) for more details.
+
+### What labels are required for each issue?
+
+At minimum, both `type` and `source` labels should be specified on each issue before moving it from the "Sorting" tab to the "Backlog" tab. All issues that are bugs should also be tagged with a `severity` label.
+
+The `type` labels are exclusive of each other: each sorted issue should have exactly one `type` label. These labels give high-level information on the issue's classification (_e.g._, bug, feature, tech debt, etc.)
 
-Please note that there are also automation policies in place. For example, if an issue is labeled as https://github.com/conda/infra/labels/pending%3A%3Afeedback and https://github.com/conda/infra/labels/unreproducible, that issue will be auto-closed after a month of inactivity.
+The `source` labels are exclusive of each other: each sorted issue should have exactly one `source` label. These labels give information on the sub-group to which the issue's author belongs (_e.g._, a partner, a frequent contributor, the wider community, etc.). Through these labels, maintainers gain insight into how well we're meeting the needs of various groups.
 
+The `severity` labels are exclusive of each other and, while required for the [`type::bug`](https://github.com/conda/infrastructure/labels/type%3A%bug) label, they can also be applied to other types to indicate demand or need. These labels help us to prioritize our work. Severity is not the only factor for work prioritization, but it is an important consideration.
 
-#### How are new labels defined?
+Please review the descriptions of the `type`, `source`, and `severity` labels on the [labels page][labels-page] prior to use.
 
-Labels are defined using a scoped syntax with an optional high-level category (_e.g._, source, tag, type, etc.) and a specific topic, much like the following:
+### How are new labels defined?
+
+Labels are defined using a scoped syntax with an optional high-level category (_e.g._, `source`, `tag`, `type`, etc.) and a specific topic, much like the following:
 
 - `[topic]`
 - `[category::topic]`
 - `[category::topic-phrase]`
 
-This syntax helps with issue sorting enforcement; at minimum, both `type` and `source` labels should be specified on each issue before moving it from "`Sorting`" to "`Backlog`".
-
-There are a number of labels that have been defined for the different `conda` projects. In order to create a streamlined sorting process, label terminologies are standardized using similar (if not the same) labels.
-
+This syntax helps with issue sorting enforcement, as it helps to ensure that sorted issues are, at minimum, categorized by type and source.
 
-#### How are new labels added?
+There are a number of labels that have been defined for the different repositories. In order to create a streamlined sorting process, label terminologies are standardized using similar (if not the same) labels.
 
-New **global** labels (_i.e._, generic labels that apply equally to all `conda` repos) can be added to the `conda/infra`'s [`.github/global.yml` file][labels-global]; new **local** labels (_i.e._, labels specific to particular `conda` repos) can be added to each repository's [`.github/labels.yml`][labels-local] file. All new labels should follow the labeling syntax described in the "How are new labels defined?" section of this document.
+### How are new labels added?
 
+New **global** labels (_i.e._, labels that apply equally to all repositories within the conda GitHub organization) are added to [`conda/infrastructure`][infrastructure]'s [`.github/global.yml` file][labels-global]; new **local** labels (_i.e._, labels specific to particular repositories) are added to each repository's [`.github/labels.yml` file][labels-local]. All new labels should follow the labeling syntax described in ["How are new labels defined?"](#how-are-new-labels-defined). Global labels are combined with any local labels and these aggregated labels are used by the [`.github/workflows/labels.yml` workflow][workflow-labels] to synchronize the labels available for the repository.
 
-#### Are there any templates to use as responses for commonly-seen issues?
+### Are there any templates to use as responses for commonly-seen issues?
 
-Some of the same types of issues appear regularly (_e.g._, issues that are duplicates of others, tickets that should be filed in the Anaconda issue tracker, errors that are due to a user's specific setup/environment, etc.).
+Some of the same types of issues appear regularly (_e.g._, issues that are duplicates of others, issues that should be filed in the Anaconda issue tracker, errors that are due to a user's specific setup/environment, etc.).
 
 Below are some boilerplate responses for the most commonly-seen issues to be sorted:
 
 <details>
 <summary><b>Duplicate Issue</b></summary>
 
+<!-- this is a code block, any links need to be embedded -->
 <pre>
 
 This is a duplicate of <b>[link to primary issue]</b>; please feel free to continue the discussion there.
 </pre>
 
 > **Warning**
-> Apply the https://github.com/conda/infra/labels/duplicate label to the issue being closed and https://github.com/conda/infra/labels/duplicate%3A%3Aprimary to the original issue.
+> Apply the https://github.com/conda/infrastructure/labels/duplicate label to the issue being closed and https://github.com/conda/infrastructure/labels/duplicate%3A%3Aprimary to the original issue.
 
 </details>
 
 <details>
 <summary><b>Requesting an Uninstall/Reinstall of <code>conda</code></b></summary>
 
+<!-- this is a code block, any links need to be embedded -->
 <pre>
 
 Please uninstall your current version of `conda` and reinstall the latest version.
@@ -202,6 +235,7 @@ whichever is more appropriate for your needs.
 <details>
 <summary><b>Redirect to Anaconda Issue Tracker</b></summary>
 
+<!-- this is a code block, any links need to be embedded -->
 <pre>
 
 Thank you for filing this issue! Unfortunately, this is off-topic for this repo.
@@ -211,13 +245,14 @@ where `conda` installer/package issues are addressed.
 </pre>
 
 > **Warning**
-> Apply the https://github.com/conda/infra/labels/off-topic label to these tickets before closing them out.
+> Apply the https://github.com/conda/infrastructure/labels/off-topic label to these issues before closing them out.
 
 </details>
 
 <details>
 <summary><b>Redirecting to Nucleus Forums</b></summary>
 
+<!-- this is a code block, any links need to be embedded -->
 <pre>
 
 Unfortunately, this issue is outside the scope of support we offer via GitHub;
@@ -226,30 +261,74 @@ please post details to the [Nucleus forums](https://community.anaconda.cloud/).
 </pre>
 
 > **Warning**
-> Apply the https://github.com/conda/infra/labels/off-topic label to these tickets before closing them out.
+> Apply the https://github.com/conda/infrastructure/labels/off-topic label to these issues before closing them out.
+
+</details>
+
+<details>
+<summary><b>Slow solving of conda environment</b></summary>
+
+<!-- this is a code block, any links need to be embedded -->
+<pre>
+Hi [@username],
+
+Thanks for voicing your concern about the performance of our dependency solver. To fix this, our official recommendation is using the "conda-libmamba-solver" instead of the default "classic" solver (more information about the "conda-libmamba-solver" can be found here: https://conda.github.io/conda-libmamba-solver/getting-started/).
+
+In most cases "conda-libmamba-solver" should be significantly faster than the "classic" solver. We hope it provides you with a much better experience going forward.
+</pre>
 
 </details>
 
-In order to not have to manually type or copy/paste the above repeatedly, please note that it's possible to add text for the most commonly-used responses via [GitHub's "Add Saved Reply" option][docs-saved-reply].
 
+In order to not have to manually type or copy/paste the above repeatedly, note that it's possible to add text for the most commonly-used responses via [GitHub's "Add Saved Reply" option][docs-saved-reply].
 
-### Commit signing
+## Commit Signing
 
 For all conda maintainers, we require commit signing and strongly recommend it for all others wishing to contribute to conda
 related projects. More information about how to set this up within GitHub can be found here:
 
-- [Signing Commits][signing-commits]
+- [GitHub's signing commits docs][docs-commit-signing]
 
-### Types of Tickets
+## Types of Issues
 
-#### Standard Ticket/Issue
+### Standard Issue
 
 TODO
 
-#### Epics
+### Epics
 
 TODO
 
-#### Spikes
+### Spikes
 
-TODO
+#### What is a spike?
+
+"Spike" is a term that is borrowed from extreme programming and agile development. They are used when the **outcome of an issue is unknown or even optional**. For example, when first coming across a problem that has not been solved before, a project may choose to either research the problem or create a prototype in order to better understand it.
+
+Additionally, spikes represent work that **may or may not actually be completed or implemented**. An example of this are prototypes created to explore possible solutions. Not all prototypes are implemented and the purpose of creating a prototype is often to explore the problem space more. For research-oriented tasks, the end result of this research may be that a feature request simply is not viable at the moment and would result in putting a stop to that work.
+
+Finally, spikes are usually **timeboxed**. However, given the open source/volunteer nature of our contributions, we do not enforce this for our contributors. When a timebox is set, this means that we are limiting how long we want someone to work on said spike. We do this to prevent contributors from falling into a rabbit hole they may never return from. Instead, we set a time limit to perform work on the spike and then have the assignee report back. If the tasks defined in the spike have not yet been completed, a decision is made on whether it makes sense to perform further work on the spike.
+
+#### When do I create a spike?
+
+A spike should be created when we do not have enough information to move forward with solving a problem. That simply means that, whenever we are dealing with unknowns or processes the project team has never encountered before, it may be useful for us to create a spike.
+
+In day-to-day work, this kind of situation may appear when new bug reports or feature requests come in that deal with problems or technologies that the project team is unfamiliar with. All issues that the project team has sufficient knowledge of should instead proceed as regular issues.
+
+#### When do I not create a spike?
+
+Below are some common scenarios where creating a spike is not appropriate:
+
+- Writing a technical specification for a feature we know how to implement
+- Design work that would go into drafting how an API is going to look and function
+- Any work that must be completed or is not optional
+
+## Working on Issues
+
+### How do I assign myself to an issue I am actively reviewing?
+
+If you do **not** have permissions, please indicate that you are working on an issue by leaving a comment. Someone who has permissions will assign you to the issue. If two weeks have passed without a pull request or an additional comment requesting information, you may be removed from the issue and the issue reassigned.
+
+If you are assigned to an issue but will not be able to continue work on it, please comment to indicate that you will no longer be working on it and press `unassign me` next to your username in the `Assignees` section of the issue page (top right).
+
+If you **do** have permissions, please assign yourself to the issue by pressing `assign myself` under the `Assignees` section of the issue page (top right).


=====================================
README.md
=====================================
@@ -2,10 +2,15 @@
 
 [![pre-commit.ci status](https://results.pre-commit.ci/badge/github/conda/conda-package-handling/main.svg)](https://results.pre-commit.ci/latest/github/conda/conda-package-handling/main)
 
-Create and extract conda packages of various formats
+Create and extract conda packages of various formats.
 
 `conda` and `conda-build` use `conda_package_handling.api` to create and extract
 conda packages. This package also provides the `cph` command line tool to
 extract, create, and convert between formats.
 
+See also
+[conda-package-streaming](https://conda.github.io/conda-package-streaming), an
+efficient library to read from new and old format .conda and .tar.bz2 conda
+packages.
+
 Full documentation at [https://conda.github.io/conda-package-handling/](https://conda.github.io/conda-package-handling/)


=====================================
RELEASE.md
=====================================
@@ -1,20 +1,28 @@
 <!-- These docs are updated and synced from https://github.com/conda/infra -->
 
-## Release Process
+<!-- (TODO: the first three links here should be updated with the `repo.url` syntax once it works!) -->
+[epic template]: https://github.com/conda/conda/issues/new?assignees=&labels=epic&template=epic.yml
+[compare]: https://github.com/conda/infrastructure/compare
+[new release]: https://github.com/conda/infrastructure/releases/new
+<!-- links -->
+[infrastructure]: https://github.com/conda/infrastructure
+[rever docs]: https://regro.github.io/rever-docs
+[release docs]: https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
+[merge conflicts]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts
+[Anaconda Recipes]: https://github.com/AnacondaRecipes/conda-feedstock
+[conda-forge]: https://github.com/conda-forge/conda-feedstock
+
+# Release Process
 
-> **Note:**
+> **Note**
 > Throughout this document are references to the version number as `YY.M.0`, this should be replaced with the correct version number. Do **not** prefix the version with a lowercase `v`.
 
-[epic template]: ../../issues/new?assignees=&labels=epic&template=epic.yml
-[rever docs]: https://regro.github.io/rever-docs
-[compare]: ../../compare
-[new release]: ../../releases/new
-[release docs]: https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
+## 1. Open the release issue and cut a release branch. (do this ~1 week prior to release)
 
-### 1. Open the Release Issue.
+> **Note**
+> The [epic template][epic template] is perfect for this; remember to remove the **`epic`** label.
 
-> **Note:**
-> The [epic template][epic template] is perfect for this, just remember to remove the https://github.com/conda/infra/labels/epic label.
+Use the issue template below to create the release issue. After creating the release issue, pin it for easy access.
 
 <details>
 <summary><code>GitHub Issue Template</code></summary>
@@ -22,41 +30,67 @@
 ```markdown
 ### Summary
 
-Placeholder for `conda YY.M.0` release.
+Placeholder for `{{ repo.name }} YY.M.0` release.
+
+| Pilot | <pilot> |
+|---|---|
+| Co-pilot | <copilot> |
 
 ### Tasks
 
-[milestone]: https://github.com/conda/conda/milestone/56
-[releases]: https://github.com/conda/conda/releases
-[main]: https://github.com/AnacondaRecipes/conda-feedstock
-[conda-forge]: https://github.com/conda-forge/conda-feedstock
+[milestone]: {{ repo.url }}/milestone/<milestone>
+[process]: {{ repo.url }}/blob/main/RELEASE.md
+[releases]: {{ repo.url }}/releases
+[main]: https://github.com/AnacondaRecipes/{{ repo.name }}-feedstock
+[conda-forge]: https://github.com/conda-forge/{{ repo.name }}-feedstock
+[ReadTheDocs]: https://readthedocs.com/projects/continuumio-{{ repo.name }}/
 
+#### The week before release week
+
+- [ ] Create release branch (named `YY.M.x`)
+- [ ] Ensure release candidates are being successfully built (see `conda-canary/label/YY.M.x`)
 - [ ] [Complete outstanding PRs][milestone]
-- [ ] Create release PR
-    - See release process https://github.com/conda/infra/issues/541
-- [ ] [Publish Release][releases]
-- [ ] Create/update `YY.M.x` branch
+- [ ] Test release candidates
+    <!-- indicate here who has signed off on testing -->
+
+#### Release week
+
+- [ ] Create release PR (see [release process][process])
+- [ ] [Publish release][releases]
+- [ ] Activate the `YY.M.x` branch on [ReadTheDocs][ReadTheDocs]
 - [ ] Feedstocks
-    - [ ] Bump version [Anaconda's main][main]
-    - [ ] Bump version [conda-forge][conda-forge]
-    - Link any other feedstock PRs that are necessary
+    - [ ] Bump version & update dependencies/tests in [Anaconda, Inc.'s feedstock][main]
+    - [ ] Bump version & update dependencies/tests in [conda-forge feedstock][conda-forge]
+    <!-- link any other feedstock PRs here -->
 - [ ] Hand off to the Anaconda packaging team
 - [ ] Announce release
-    - [ ] Slack
-    - [ ] Twitter
+    - Blog Post (optional)
+        - [ ] conda.org (link to pull request)
+    - Long form
+        - [ ] Create release [announcement draft](https://github.com/conda/communications)
+        - [ ] [Discourse](https://conda.discourse.group/)
+        - [ ] [Matrix (conda/conda)](https://matrix.to/#/#conda_conda:gitter.im) (this auto posts from Discourse)
+    - Summary
+        - [ ] [Twitter](https://twitter.com/condaproject)
 ```
-
 </details>
 
 
-### 2. Ensure `rever.xsh` and `news/TEMPLATE` are up to date.
+> **Note**
+> The new release branch should adhere to the naming convention of `YY.M.x`.
 
-These are synced from https://github.com/conda/infra.
+## 2. Alert various parties of the upcoming release. (do this ~1 week prior to release)
+
+Let various interested parties know about the upcoming release; at minimum, conda-forge maintainers should be informed. For major features, a blog post describing the new features should be prepared and posted once the release is completed (see the announcements section of the release issue).
+
+## 3. Ensure `rever.xsh` and `news/TEMPLATE` are up to date.
+
+These are synced from [`conda/infrastructure`][infrastructure].
 
 <details>
-<summary><h3>3. Run Rever.</h3></summary>
+<summary><h2>4. Run rever. (ideally done on the Monday of release week)</h2></summary>
 
-Currently, there are only 2 activities we use rever for, (1) aggregating the authors and (2) updating the changelog. Aggregating the authors can be an error-prone process and also suffers from builtin race conditions (i.e. to generate an updated `.authors.yml` we need an updated `.mailmap` but to have an updated `.mailmap` we need an updated `.authors.yml`). This is why the following steps are very heavy-handed (and potentially repetitive) in running rever commands, undoing commits, squashing/reordering commits, etc.
+Currently, there are only 2 activities we use rever for, (1) aggregating the authors and (2) updating the changelog. Aggregating the authors can be an error-prone process and also suffers from builtin race conditions (_i.e._, to generate an updated `.authors.yml` we need an updated `.mailmap` but to have an updated `.mailmap` we need an updated `.authors.yml`). This is why the following steps are very heavy-handed (and potentially repetitive) in running rever commands, undoing commits, squashing/reordering commits, etc.
 
 1. Install [`rever`][rever docs] and activate the environment:
 
@@ -69,19 +103,26 @@ Currently, there are only 2 activities we use rever for, (1) aggregating the aut
 2. Clone and `cd` into the repository if you haven't done so already:
 
     ```bash
-    (rever) $ git clone git at github.com:conda/conda.git
+    (rever) $ git clone git at github.com:{{ repo.user }}/{{ repo.name }}.git
     (rever) $ cd conda
     ```
 
-2. Create a release branch:
+2. Fetch the latest changes from the remote and checkout the release branch created a week ago:
 
     ```bash
-    (rever) $ git checkout -b release-YY.M.0
+    (rever) $ git fetch upstream
+    (rever) $ git checkout YY.M.x
+    ```
+
+2. Create a versioned branch, this is where rever will make its changes:
+
+    ```bash
+    (rever) $ git checkout -b changelog-YY.M.0
     ```
 
 2. Run `rever --activities authors`:
 
-    > **Note:**
+    > **Note**
     > Include `--force` when re-running any rever commands for the same `<VERSION>`, otherwise, rever will skip the activity and no changes will be made (i.e., rever remembers if an activity has been run for a given version).
 
     ```bash
@@ -162,13 +203,13 @@ Currently, there are only 2 activities we use rever for, (1) aggregating the aut
 
 4. Review news snippets (ensure they are all using the correct Markdown format, **not** reStructuredText) and add additional snippets for undocumented PRs/changes as necessary.
 
-    > **Note:**
+    > **Note**
     > We've found it useful to name news snippets with the following format: `<PR #>-<DESCRIPTIVE SLUG>`.
     >
     > We've also found that we like to include the PR #s inline with the text itself, e.g.:
     >
     > ```markdown
-    > ### Enhancements
+    > ## Enhancements
     >
     > * Add `win-arm64` as a known platform (subdir). (#11778)
     > ```
@@ -195,7 +236,7 @@ Currently, there are only 2 activities we use rever for, (1) aggregating the aut
 
 5. Run `rever --activities changelog`:
 
-    > **Note:**
+    > **Note**
     > This has previously been a notoriously fickle step (likely due to incorrect regex patterns in the `rever.xsh` config file and missing `github` keys in `.authors.yml`) so beware of potential hiccups. If this fails, it's highly likely to be an innocent issue.
 
     ```bash
@@ -260,19 +301,19 @@ Currently, there are only 2 activities we use rever for, (1) aggregating the aut
         + 93fdf029fd4cf235872c12cab12a1f7e8f95a755 Added first contributions
         ```
 
-8. Push this release branch:
+8. Push this versioned branch.
 
     ```bash
-    (rever) $ git push -u upstream release-YY.M.0
+    (rever) $ git push -u upstream changelog-YY.M.0
     ```
 
-9. Open the Release PR.
+9. Open the Release PR targing the `YY.M.x` branch.
 
     <details>
     <summary>GitHub PR Template</summary>
 
     ```markdown
-    ### Description
+    ## Description
 
     ✂️ snip snip ✂️ the making of a new release.
 
@@ -281,40 +322,61 @@ Currently, there are only 2 activities we use rever for, (1) aggregating the aut
 
     </details>
 
-10. Update Release Issue to include a link to the Release PR.
+10. Update release issue to include a link to the release PR.
 
 11. [Create][new release] the release and **SAVE AS A DRAFT** with the following values:
 
-    > **Note:**
-    > Only publish the release after the Release PR is merged, until then always **save as draft**.
+    > **Note**
+    > Only publish the release after the release PR is merged, until then always **save as draft**.
 
     | Field | Value |
     |---|---|
     | Choose a tag | `YY.M.0` |
-    | Target | `main` |
+    | Target | `YY.M.x` |
     | Body | copy/paste blurb from `CHANGELOG.md` |
 
 </details>
 
-### 4. Wait for review and approval of Release PR.
+## 5. Wait for review and approval of release PR.
+
+## 6. Merge release PR and publish release.
+
+## 7. Merge/cherry pick the release branch over to the `main` branch.
+
+<details>
+<summary>Internal process</summary>
 
-### 5. Merge Release PR and Publish Release.
+1. From the main "< > Code" page of the repository, select the drop down menu next to the `main` branch button and then select "View all branches" at the very bottom.
 
-### 6. Create a new branch (`YY.M.x`) corresponding with the release.
+2. Find the applicable `YY.MM.x` branch and click the "New pull request" button.
+
+3. "Base" should point to `main` while "Compare" should point to `YY.MM.x`.
+
+4. Ensure that all of the commits being pulled in look accurate, then select "Create pull request".
+
+> **Note**
+> Make sure NOT to push the "Update Branch" button. If there are [merge conflicts][merge conflicts], create a temporary "connector branch" dedicated to fixing merge conflicts separately from the `YY.M.0` and `main` branches.
+
+5. Review and merge the pull request the same as any code change pull request.
+
+> **Note**
+> The commits from the release branch need to be retained in order to be able to compare individual commits; in other words, a "merge commit" is required when merging the resulting pull request vs. a "squash merge". Protected branches will require permissions to be temporarily relaxed in order to enable this action.
+
+</details>
 
-### 7. Open PRs to bump main and conda-forge feedstocks to use `YY.M.0`.
+## 8. Open PRs to bump [Anaconda Recipes][Anaconda Recipes] and [conda-forge][conda-forge] feedstocks to use `YY.M.0`.
 
-### 8. Hand off to Anaconda's packaging team.
+## 9. Hand off to Anaconda's packaging team.
 
 <details>
 <summary>Internal process</summary>
 
-1. Open packaging request in #package_requests, include links to the Release PR and feedstock PRs.
+1. Open packaging request in #package_requests Slack channel, include links to the Release PR and feedstock PRs.
 
 2. Message packaging team/PM to let them know that a release has occurred and that you are the release manager.
 
 </details>
 
-### 9. Continue championing and shepherding.
+## 10. Continue championing and shepherding.
 
-Remember to continue updating the Release Issue with the latest details as tasks are completed.
+Remember to make all relevant announcements and continue to update the release issue with the latest details as tasks are completed.


=====================================
conda.recipe/meta.yaml
=====================================
@@ -25,7 +25,7 @@ requirements:
     - wheel
   run:
     - python
-    - conda-package-streaming >=0.7.0
+    - conda-package-streaming >=0.9.0
 
 test:
   source_files:
@@ -49,7 +49,7 @@ about:
   license_family: BSD
   license_file:
     - LICENSE
-  summary: Create and extract conda packages of various formats
+  summary: Create and extract conda packages of various formats.
 
 extra:
   recipe-maintainers:


=====================================
docs/requirements.txt
=====================================
@@ -1,5 +1,5 @@
 # used in sphinx documentation build
-conda-package-streaming>=0.7.0
+conda-package-streaming>=0.9.0
 # docs
 furo
 sphinx


=====================================
rever.xsh
=====================================
@@ -1,4 +1,4 @@
-$ACTIVITIES = ["version_bump", "authors", "changelog"]
+$ACTIVITIES = ["authors", "changelog"]
 
 # Basic settings
 $PROJECT = $GITHUB_REPO = $(basename $(git remote get-url origin)).split('.')[0].strip()
@@ -27,6 +27,8 @@ $CHANGELOG_CATEGORY_TITLE_FORMAT = "### {category}\n\n"
 $CHANGELOG_AUTHORS_TITLE = "Contributors"
 $CHANGELOG_AUTHORS_FORMAT = "* @{github}\n"
 
-$VERSION_BUMP_PATTERNS = [  # These note where/how to find the version numbers
-    ('src/conda_package_handling/__init__.py', r'__version__\s*=.*', '__version__ = "$VERSION"'),
-]
+try:
+    # allow repository to customize synchronized-from-infa rever config
+    from rever_overrides import *
+except ImportError:
+    pass


=====================================
rever_overrides.xsh
=====================================
@@ -0,0 +1,6 @@
+# override synced-from-infra rever.xsh
+$ACTIVITIES = ["version_bump", "authors", "changelog"]
+
+$VERSION_BUMP_PATTERNS = [  # These note where/how to find the version numbers
+    ('src/conda_package_handling/__init__.py', r'__version__\s*=.*', '__version__ = "$VERSION"'),
+]


=====================================
setup.py
=====================================
@@ -13,7 +13,9 @@ version = module.__version__
 setup(
     name="conda-package-handling",
     version=version,
-    description="Create and extract conda packages of various formats",
+    description="Create and extract conda packages of various formats.",
+    long_description=open("README.md").read(),
+    long_description_content_type="text/markdown",
     author="Anaconda, Inc.",
     author_email="conda at anaconda.com",
     url="https://github.com/conda/conda-package-handling",
@@ -23,7 +25,7 @@ setup(
     keywords="conda-package-handling",
     classifiers=["Programming Language :: Python :: 3"],
     python_requires=">=3.7",
-    install_requires=["conda-package-streaming >= 0.7.0"],
+    install_requires=["conda-package-streaming >= 0.9.0"],
     extras_require={
         "docs": ["furo", "sphinx", "sphinx-argparse", "myst-parser", "mdit-py-plugins>=0.3.0"],
         "test": ["mock", "pytest", "pytest-cov", "pytest-mock"],


=====================================
src/conda_package_handling/__init__.py
=====================================
@@ -1 +1 @@
-__version__ = "2.1.0"
+__version__ = "2.2.0"



View it on GitLab: https://salsa.debian.org/med-team/conda-package-handling/-/commit/9c76bb452a2e9098877607204835348f3de0311a

-- 
View it on GitLab: https://salsa.debian.org/med-team/conda-package-handling/-/commit/9c76bb452a2e9098877607204835348f3de0311a
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-med-commit/attachments/20230911/f1b3264d/attachment-0001.htm>


More information about the debian-med-commit mailing list