Skip to content

Prepare release v336#2038

Merged
heroku-linguist[bot] merged 1 commit intomainfrom
prepare-release
Mar 2, 2026
Merged

Prepare release v336#2038
heroku-linguist[bot] merged 1 commit intomainfrom
prepare-release

Conversation

@heroku-linguist
Copy link
Contributor

@heroku-linguist heroku-linguist bot commented Feb 26, 2026

Commits since the last release:

For the full diff, see the compare view:
v335...main

@heroku-linguist heroku-linguist bot requested a review from edmorley as a code owner February 26, 2026 11:31
@heroku-linguist heroku-linguist bot enabled auto-merge (squash) February 26, 2026 11:31
@heroku-linguist heroku-linguist bot merged commit a6e6ac0 into main Mar 2, 2026
5 of 6 checks passed
@heroku-linguist heroku-linguist bot deleted the prepare-release branch March 2, 2026 17:24
@edmorley
Copy link
Member

edmorley commented Mar 2, 2026

$ make publish
Checking environment...
Checking buildpack versions in sync...
Extracting changelog entry for this release...

- Added a workaround for `nltk.txt` package downloader errors caused by an upstream regression in NLTK v3.9.3. ([#2041](https://github.com/heroku/heroku-buildpack-python/pull/2041))
- Changed the S3 URL used to download Python to use AWS' dual-stack (IPv6 compatible) endpoint. ([#2035](https://github.com/heroku/heroku-buildpack-python/pull/2035))

Deploy as v336 [y/n]? y

Creating GitHub release...
https://github.com/heroku/heroku-buildpack-python/releases/tag/v336

Publishing to the Heroku Buildpack Registry...
Two-factor code: ********************************************
Publishing buildpack heroku/python... done
Publishing buildpack was successful

 Version Released At              Status    
 ─────── ──────────────────────── ───────── 
 336     2026-03-02T17:29:33.136Z published 

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant