Resolve conflict

Author: hugovk

.github/workflows/ci.yml

@@ -35,7 +35,7 @@ jobs:
         run: bun install --frozen-lockfile
 
       - name: Run prek
-        uses: j178/prek-action@v2.0.5
+        uses: j178/prek-action@v3.0.0
 
   build:
     name: Build

.github/workflows/deploy.yml

@@ -49,7 +49,7 @@ jobs:
         run: bunx astro check
 
       - name: Spell check
-        uses: crate-ci/typos@v1.48.0
+        uses: crate-ci/typos@v1.49.0
 
       - name: Build
         run: bun run build

bun.lock

@@ -1,6 +1,6 @@
 {
   "name": "Stan Ulbrych",
-  "bio": "Python patcher, PSRT member, and translator",
+  "bio": "Python core team, PSRT, and Docs WG member",
   "github": "StanFromIreland",
   "avatar": "",
   "bluesky": "stan.ulbrych.org",

content/authors/stan-ulbrych.json

@@ -0,0 +1,40 @@
+---
+title: "Announcing the Packaging Council Election Candidates for 2026!"
+publishDate: "2026-08-13"
+author: Pradyun Gedam
+description: "Announcing the 17 nominees for the inaugural Python Packaging Council election, and how to vote in the election."
+published: true
+---
+
+What an exciting list! Please take a look at who is running for the inaugural Python Packaging Council (PPC) [on the Nominees page](https://www.python.org/nominations/elections/2026-python-packaging-council/nominees/). This election has 17 nominees for 5 open seats on the council.
+
+## Election Overview
+
+This inaugural election fills all five seats on the PPC. The two candidates receiving the highest number of votes shall be designated Cohort A with a two year term, and the three candidates receiving the next highest number of votes shall be designated Cohort B with a one year term.
+
+In future elections, each cohort will be elected for a full two-year term in alternating years, so that roughly half of the PPC turns over each cycle.
+
+### Election Timeline
+
+- Nominations open: Tuesday, July 28th, 2:00 pm UTC
+- Nomination cut-off: Tuesday, August 11th, 2:00 pm UTC
+- **Announce candidates: Thursday, August 13th**
+- Voter affirmation cut-off: Tuesday, August 25th, 2:00 pm UTC
+- Voting start date: Tuesday, September 1st, 2:00 pm UTC
+- Voting end date: Tuesday, September 15th, 2:00 pm UTC
+
+Not sure what UTC is for you locally? Check this [UTC time converter](https://savvytime.com/converter/utc)!
+
+## Reminder: Affirm your intention to vote
+
+**If you wish to vote in this election, you must affirm your intention to vote no later than Tuesday, August 25th, 2:00 pm UTC, to participate in this election**.
+
+Every PSF Voting Member (Supporting, Contributing, and Fellow) needs to affirm their membership to vote in this election. Find more information, including step-by-step instructions on voting affirmation, in our ["Affirm Your PSF Membership Voting Status" blog post](https://pyfound.blogspot.com/2026/07/affirm-PSF-voting-status-2026.html).
+
+If you run into any issues, or have questions about your membership, please contact [pc-elections@python.org](mailto:pc-elections@python.org).
+
+## Voting: What to expect
+
+If you are a voting member of the PSF that affirmed your intention to participate in this election, you will receive an email from "OpaVote Voting Link \<[noreply@opavote.com](mailto:noreply@opavote.com)\>" with your ballot -- the subject line will read "Python Packaging Council Election 2026" on September 1st. If you don't receive a ballot as expected, please first check your spam folder for a message from "[noreply@opavote.com](mailto:noreply@opavote.com)".
+
+If you don't see anything, please get in touch by emailing [pc-elections@python.org](mailto:pc-elections@python.org) so we can look into your account and make sure we have the most up-to-date email for you.

content/posts/2026-packaging-council-nominees/index.md

@@ -11,7 +11,7 @@ published: true
 ---
 ![Stacked area chart showing CPython's growth from a few lines in 1990 to 2.9 million lines in 2026, broken down by language](cpython_growth.svg)
 
-([Click to zoom!](https://blog.python.org/_astro/cpython_growth.CDpb_itO_ZomrED.svg))
+(Open the image in a new tab for better zooming!)
 
 While working on a patch and navigating through CPython, I got curious as to how the codebase has grown over the years. Using an interesting tool I found on the internet to *count lines of code* ([cloc](https://github.com/AlDanial/cloc)), some scripts, and some patience (thank goodness for multiple cores, or I’d be at this all day), I amassed a [1,392 commit dataset.](https://gist.github.com/StanFromIreland/bd33d5ee3c59c54cbe1f3bad2fbdb4e9) With that, and some Git spelunking for the annotations, I was able to generate the above graph.