[ONBOARD] Remove UV buildpack from pipeline apps

[paribaker]

Overview

Remove the UV buildpack from the Heroku pipeline app configuration. The UV buildpack (heroku-buildpack-uv) was previously used as a Python package manager but is no longer needed for our deployment setup. Removing it will simplify the buildpack stack and reduce build times.

What You'll Learn

• Working with Heroku buildpacks and build configuration
• Understanding the justfile command syntax (Just command runner)
• How Heroku buildpack ordering works
• Shell scripting patterns used in this codebase

Task Description

Modify the heroku-create-pipeline command in the justfile to remove the UV buildpack from the buildpack stack. Currently, three buildpacks are added to each app - you'll remove the UV one while keeping the others.

Requirements

• Remove the UV buildpack line from the heroku-create-pipeline command
• Keep the heroku/nodejs and heroku/python buildpacks intact
• Ensure the remaining buildpack order is correct

Reference Files

Study these files to understand the patterns:

Justfile Commands

• justfile:313-398 - The heroku-create-pipeline command where the buildpack is configured
  • Line 323: Initial buildpack added during app creation (heroku/nodejs)
  • Line 324: UV buildpack to remove (https://github.com/dropseed/heroku-buildpack-uv.git)
  • Line 325: Python buildpack (heroku/python)
  • Lines 322-339: The loop that applies these settings to both staging and production apps

Related Commands

• justfile:446-454 - heroku-create-app for reference (note: this one doesn't add buildpacks)

Implementation Hints

1. Start here: Look at line 324 in the justfile - this is the line to remove
2. Location: The UV buildpack is added inside the for APP_NAME in $STAGING $PRODUCTION; do loop
3. Simple change: This is a single line deletion - just remove line 324
4. Verify: After removal, the buildpack stack should only have heroku/nodejs and heroku/python

Acceptance Criteria

• UV buildpack line is removed from the heroku-create-pipeline command
• heroku/nodejs buildpack remains as the first buildpack
• heroku/python buildpack remains and is added after nodejs
• The command runs successfully without errors when creating a new pipeline
• Code follows existing patterns in the codebase

Resources

• Heroku Buildpacks Documentation
• Heroku Buildpack CLI Reference
• Just Command Runner Documentation

[nimble-claude]

Hi! I've investigated this issue and found that the UV buildpack was already removed in PR #31 (commit 70ade63) back in July 2025.

The change that was described in this issue (removing line 324 from the justfile which added https://github.com/dropseed/heroku-buildpack-uv.git) has already been completed.

Current state of the heroku-create-pipeline command in justfile (lines 286-288):

for APP_NAME in $STAGING $PRODUCTION; do
  heroku apps:create $APP_NAME --no-remote --buildpack=heroku/nodejs --team=$TEAM
  heroku buildpacks:add heroku/python --app=$APP_NAME

The buildpack stack now only contains:

1. heroku/nodejs (added during app creation)
2. heroku/python (added after)

The UV buildpack has been successfully removed. Since this is marked as an [ONBOARD] issue created after the work was completed, this may have been intended as a practice task. Should this issue be closed, or would you like me to help with something else?