@webknjaz Any idea why the chronographer didn't catch CHANGES files?

Codecov Report

Merging #6139 (f349b0f) into master (45c38f2) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6139      +/-   ##
==========================================
- Coverage   93.32%   93.32%   -0.01%     
==========================================
  Files         102      102              
  Lines       30140    30166      +26     
  Branches     2696     2699       +3     
==========================================
+ Hits        28129    28151      +22     
- Misses       1837     1840       +3     
- Partials      174      175       +1     

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 45c38f2...f349b0f. Read the comment docs.

@asvetlov

@webknjaz Any idea why the chronographer didn't catch CHANGES files?

Because you named them wrong. The number should go after the type.
CHANGES/6139.1.feature -> CHANGES/6139.feature.1.

By the way, we now have a Sphinx integration that also shows unreleased change notes. See https://aiohttp--6139.org.readthedocs.build/en/6139/changes.html#to-be-included-in-vrelease-if-present.

Look closer and you'll see that your names confused Towncrier and it linked issues #1 and #2 to your change notes and not #6139.

Aha, thanks!

Backport to 3.8: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 00d5286 on top of patchback/backports/3.8/00d52864eeea43d18ad022c7cb0e80d9741e32b9/pr-6139

Backporting merged PR #6139 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.8/00d52864eeea43d18ad022c7cb0e80d9741e32b9/pr-6139 upstream/3.8

4. Now, cherry-pick PR Setup binary builds for Alpine and MacOS arm #6139 contents into that branch:

   $ git cherry-pick -x 00d52864eeea43d18ad022c7cb0e80d9741e32b9

   If it'll yell at you with something like fatal: Commit 00d52864eeea43d18ad022c7cb0e80d9741e32b9 is a merge but no -m option was given., add -m 1 as follows intead:

   $ git cherry-pick -m1 -x 00d52864eeea43d18ad022c7cb0e80d9741e32b9

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Setup binary builds for Alpine and MacOS arm #6139 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.8/00d52864eeea43d18ad022c7cb0e80d9741e32b9/pr-6139

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

💔 Backport was not successful

The PR was attempted backported to the following branches:

• ❌ 3.8: Commit could not be cherrypicked due to conflicts

Backported by d8efd32