🤖 updated file(s)

.github/workflows/update.yml

@@ -80,7 +80,7 @@ jobs:
       - if: github.event.comment.body != '@conda-bot render'
         id: create
         # no-op if no commits were made
-        uses: peter-evans/create-pull-request@5e914681df9dc83aa4e4905692ca88beb2f9e91f # v7.0.5
+        uses: peter-evans/create-pull-request@67ccf781d68cd99b580ae25a5c18a1cc84ffff1f # v7.0.6
         with:
           push-to-fork: ${{ env.FORK }}
           token: ${{ secrets.SYNC_TOKEN }}

RELEASE.md

@@ -13,12 +13,12 @@
 # Release Process
 
 > [!NOTE]
-> Throughout this document are references to the version number as `MAJOR.MINOR`, this should be replaced with the correct version number. Do **not** prefix the version with a lowercase `v`.
+> Throughout this document are references to the version number as `MAJOR.MINOR.MINOR`, this should be replaced with the correct version number. Do **not** prefix the version with a lowercase `v`.
 
 ## 1. Open the release issue and cut a release branch. (do this ~1 week prior to release)
 
 > [!NOTE]
-> The new release branch should adhere to the naming convention of `` (note the difference to `MAJOR.MINOR`). In the case of patch/hotfix releases, however, do NOT cut a new release branch; instead, use the previously-cut `` release branch.
+> The new release branch should adhere to the naming convention of `MAJOR.MINOR.x` (note the difference to `MAJOR.MINOR.MINOR`). In the case of patch/hotfix releases, however, do NOT cut a new release branch; instead, use the previously-cut `MAJOR.MINOR.x` release branch.
 
 Use the issue template below to create the release issue. After creating the release issue, pin it for easy access.
 
@@ -28,7 +28,7 @@ Use the issue template below to create the release issue. After creating the rel
 ```markdown
 ### Summary
 
-Placeholder for `conda-package-handling ` release.
+Placeholder for `conda-package-handling MAJOR.MINOR.x` release.
 
 | Pilot | <pilot> |
 |---|---|
@@ -46,8 +46,8 @@ Placeholder for `conda-package-handling ` release.
 <details open>  <!-- feel free to remove the open attribute once this section is completed -->
 <summary><h4>The week before release week</h4></summary>
 
-- [ ] Create release branch (named ``)
-- [ ] Ensure release candidates are being successfully built (see `conda-canary/label/rc-conda-package-handling-`)
+- [ ] Create release branch (named `MAJOR.MINOR.x`)
+- [ ] Ensure release candidates are being successfully built (see `conda-canary/label/rc-conda-package-handling-MAJOR.MINOR.x`)
 - [ ] [Complete outstanding PRs][milestone]
 - [ ] Test release candidates
     <!-- indicate here who has signed off on testing -->
@@ -59,8 +59,8 @@ Placeholder for `conda-package-handling ` release.
 
 - [ ] Create release PR (see [release process][process])
 - [ ] [Publish release][releases]
-- [ ] Merge `` back into `main`
-- [ ] Activate the `` branch on [ReadTheDocs][ReadTheDocs]
+- [ ] Merge `MAJOR.MINOR.x` back into `main`
+- [ ] Activate the `MAJOR.MINOR.x` branch on [ReadTheDocs][ReadTheDocs]
 - [ ] Feedstocks
     - [ ] Bump version & update dependencies/tests in [Anaconda, Inc.'s feedstock][main]
     - [ ] Bump version & update dependencies/tests in [conda-forge feedstock][conda-forge]
@@ -87,12 +87,12 @@ If a patch release is necessary, reopen the original release issue and append th
 
 ```markdown
 <details open>  <!-- feel free to remove the open attribute once this section is completed -->
-<summary><h4>Patch MAJOR.MINOR</h4></summary>
+<summary><h4>Patch MAJOR.MINOR.MINOR</h4></summary>
 
 - [ ] <!-- list issues & PRs that need to be resolved here -->
 - [ ] Create release PR (see [release process][process])
 - [ ] [Publish release][releases]
-- [ ] Merge `` back into `main`
+- [ ] Merge `MAJOR.MINOR.x` back into `main`
 - [ ] Feedstocks
     - [ ] Bump version & update dependencies/tests in [Anaconda, Inc.'s feedstock][main]
     - [ ] Bump version & update dependencies/tests in [conda-forge feedstock][conda-forge]
@@ -117,7 +117,7 @@ Let various interested parties know about the upcoming release; at minimum, cond
 
 ### Canary Builds for Manual Testing
 
-Once the release PRs are filed, successful canary builds will be available on `/conda-package-handling/files?channel=rc-conda-package-handling-` for manual testing.
+Once the release PRs are filed, successful canary builds will be available on `https://anaconda.org/conda-canary/conda-package-handling/files?channel=rc-conda-package-handling-MAJOR.MINOR.x` for manual testing.
 
 > [!NOTE]
 > You do not need to apply the `build::review` label for release PRs; every commit to the release branch builds and uploads canary builds to the respective `rc-` label.
@@ -150,13 +150,13 @@ Currently, there are only 2 activities we use rever for, (1) aggregating the aut
 
     ```bash
     (rever) $ git fetch upstream
-    (rever) $ git checkout 
+    (rever) $ git checkout MAJOR.MINOR.x
     ```
 
 2. Create a versioned branch, this is where rever will make its changes:
 
     ```bash
-    (rever) $ git checkout -b changelog-MAJOR.MINOR
+    (rever) $ git checkout -b changelog-MAJOR.MINOR.MINOR
     ```
 
 2. Run `rever --activities authors <VERSION>`:
@@ -184,7 +184,7 @@ Currently, there are only 2 activities we use rever for, (1) aggregating the aut
     - Here's a sample run where we undo the commit made by rever in order to commit the changes to `.authors.yml` separately:
 
         ```bash
-        (rever) $ rever --activities authors --force MAJOR.MINOR
+        (rever) $ rever --activities authors --force MAJOR.MINOR.MINOR
 
         # changes were made to .authors.yml as per the prior bullet
         (rever) $ git diff --name-only HEAD HEAD~1
@@ -313,8 +313,8 @@ Currently, there are only 2 activities we use rever for, (1) aggregating the aut
         + 86957814cf235879498ed7806029b8ff5f400034 Update .authors.yml
         + 3ec7491f2f58494a62f1491987d66f499f8113ad Update .mailmap
         + 432a9e1b41a3dec8f95a7556632f9a93fdf029fd Update news
-        + a5c0db938893d2c12cab12a1f7eb3e646ed80373 Update authorship for MAJOR.MINOR
-        + 5e95169d0df4bcdc2da9a6ba4a2561d90e49f75d Update CHANGELOG for MAJOR.MINOR
+        + a5c0db938893d2c12cab12a1f7eb3e646ed80373 Update authorship for MAJOR.MINOR.MINOR
+        + 5e95169d0df4bcdc2da9a6ba4a2561d90e49f75d Update CHANGELOG for MAJOR.MINOR.MINOR
         ```
 
 7. Since rever does not include stats on first-time contributors, we will need to add this manually.
@@ -335,18 +335,18 @@ Currently, there are only 2 activities we use rever for, (1) aggregating the aut
         + 86957814cf235879498ed7806029b8ff5f400034 Update .authors.yml
         + 3ec7491f2f58494a62f1491987d66f499f8113ad Update .mailmap
         + 432a9e1b41a3dec8f95a7556632f9a93fdf029fd Update news
-        + a5c0db938893d2c12cab12a1f7eb3e646ed80373 Update authorship for MAJOR.MINOR
-        + 5e95169d0df4bcdc2da9a6ba4a2561d90e49f75d Update CHANGELOG for MAJOR.MINOR
+        + a5c0db938893d2c12cab12a1f7eb3e646ed80373 Update authorship for MAJOR.MINOR.MINOR
+        + 5e95169d0df4bcdc2da9a6ba4a2561d90e49f75d Update CHANGELOG for MAJOR.MINOR.MINOR
         + 93fdf029fd4cf235872c12cab12a1f7e8f95a755 Add first-time contributions
         ```
 
 8. Push this versioned branch.
 
     ```bash
-    (rever) $ git push -u upstream changelog-MAJOR.MINOR
+    (rever) $ git push -u upstream changelog-MAJOR.MINOR.MINOR
     ```
 
-9. Open the Release PR targeting the `` branch.
+9. Open the Release PR targeting the `MAJOR.MINOR.x` branch.
 
     <details>
     <summary>GitHub PR Template</summary>
@@ -370,8 +370,8 @@ Currently, there are only 2 activities we use rever for, (1) aggregating the aut
 
     | Field | Value |
     |---|---|
-    | Choose a tag | `MAJOR.MINOR` |
-    | Target | `` |
+    | Choose a tag | `MAJOR.MINOR.MINOR` |
+    | Target | `MAJOR.MINOR.x` |
     | Body | copy/paste blurb from `CHANGELOG.md` |
 
 </details>
@@ -392,14 +392,14 @@ To publish the release, go to the project's release page (e.g., https://github.c
 
 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.
 
-2. Find the applicable `` branch and click the "New pull request" button.
+2. Find the applicable `MAJOR.MINOR.x` branch and click the "New pull request" button.
 
-3. "Base" should point to `main` while "Compare" should point to ``.
+3. "Base" should point to `main` while "Compare" should point to `MAJOR.MINOR.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 `` and `main` branches.
+> 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 `MAJOR.MINOR.x` and `main` branches.
 
 5. Review and merge the pull request the same as any code change pull request.
 
@@ -408,7 +408,7 @@ To publish the release, go to the project's release page (e.g., https://github.c
 
 </details>
 
-## 9. Open PRs to bump [Anaconda Recipes][Anaconda Recipes] and [conda-forge][conda-forge] feedstocks to use `MAJOR.MINOR`.
+## 9. Open PRs to bump [Anaconda Recipes][Anaconda Recipes] and [conda-forge][conda-forge] feedstocks to use `MAJOR.MINOR.MINOR`.
 
 > [!NOTE]
 > Conda-forge's PRs will be auto-created via the `regro-cf-autotick-bot`. Follow the instructions below if any changes need to be made to the recipe that were not automatically added (these instructions are only necessary for anyone who is _not_ a conda-forge feedstock maintainer, since maintainers can push changes directly to the autotick branch):