feat: provide shebang command with context of what got cloned by levibostian · Pull Request #185 · levibostian/decaf

levibostian · 2026-05-24T12:09:47Z

Related GitHub Issues

Problem

I am writing a shebang script now and I realized that if I had this information, I would be able to conditionally choose between downloading a pre-built binary of running the deno script.

Solution

Provide 2 environment variables when shebang scripts run. The shebang script can use env vars conditionally.

Testing

Added automated tests.
Manually tested. If you check this box, provide instructions for others to test, too.

Created a gist:

#!/usr/bin/env node

console.log(`name...${process.env.DECAF_SHEBANG_REF_NAME}...`)
console.log(`type...${process.env.DECAF_SHEBANG_REF}...`)

and run it, expecting to see the env vars.

Notes for reviewers

I am writing a shebang script now and I realized that if I had this information, I would be able to conditionally choose between downloading a pre-built binary of running the deno script.

github-actions · 2026-05-24T12:10:01Z

decaf

Running deployments in test mode. Results will appear below.
If this pull request and all of it's parent pull requests are merged using the...

...🟩 squash 🟩 merge method... 🚢 The next version of the project will be: 0.16.0

Learn more

Latest release: 0.15.0
Commit of latest release: 8478d77

Commits since last release:
- feat: provide shebang command with context of what got cloned

Related GitHub Issues

Problem

I am writing a shebang script now and I realized that if I had this information, I would be able to conditionally choose between downloading a pre-built binary of running the deno script.

Solution

Provide 2 environment variables when shebang scripts run. The shebang script can use env vars conditionally.

Testing

Added automated tests.
Manually tested. If you check this box, provide instructions for others to test, too.

Created a gist:

#!/usr/bin/env node

console.log(`name...${process.env.DECAF_SHEBANG_REF_NAME}...`)
console.log(`type...${process.env.DECAF_SHEBANG_REF}...`)

and run it, expecting to see the env vars.

Notes for reviewers

- chore(deps): update dependency deno to v2.8.0 (#184)

This PR contains the following updates:

Package	Update	Change
deno	minor	`2.7.14` →
`2.8.0`

Release Notes

denoland/deno (deno)

v2.8.0

Compare
Source

Configuration

📅 Schedule: (in timezone America/Chicago)

Branch creation
- Only on Sunday and Saturday (* * * * 0,6)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update
again.

If you want to rebase/retry this PR, check
this box

This PR was generated by Mend Renovate.
View the repository job
log.

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
- ci: delete lockfile update workflow (#183)

follow-up to: #181 where we
just delete the file that was commented out. it's not needed anymore
after testing success without it.
- chore(deps): lock file maintenance (#182)

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency
versions.

Configuration

📅 Schedule: (in timezone America/Chicago)

Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get
config
help if
that's undesired.

If you want to rebase/retry this PR, check
this box

This PR was generated by Mend Renovate.
View the repository job
log.

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
- ci: disable deno frozen lock-file to make CI/renovatebot setup less complex (#181)

Problem

having frozen lock file has been really annoying, but especially because
of renovatebot.

even with frozen disabled, from my understanding, deno still uses lock
files. I dont have a lot of experience with the default deno behavior
where frozen is off but lock files are on. I want to try it out.

there is a new feature being added to renovatebot that allows you to
tell renovatebot to run '--frozen false' but I am not sure when it will
be launched. when it does, we could enable frozen in the deno.jsonc
again and still not need the github action for updating lock file.

Solution

disable frozen lock files from deno config so we use the default
behavior.

Testing

Added automated tests.
Manually tested. If you check this box, provide instructions for
others to test, too.

After merging this PR, I am going to run renovatebot to see if it
successfully updates some deno dependencies and also the lock file.

Notes for reviewers

- build: simplify AGENTS.md and reduce token usage running tests (#180)

Related GitHub Issues

Problem

AGENTS.md uses too many tokens.

when you run tests, it adds the entire stdout to context.
I tend to use very small and simple files with less stuff in it.
let's try deleting a ton of the content.

Solution

tell agent to use junit report for finding failures to fix
remove everything except commands to run.

Testing

Added automated tests.
Manually tested. If you check this box, provide instructions for
others to test, too.

Notes for reviewers

...🟩 rebase 🟩 merge method... 🚢 The next version of the project will be: 0.16.0

Learn more

Latest release: 0.15.0
Commit of latest release: 8478d77

Commits since last release:
- feat: shebang command provides information on what got cloned

I am writing a shebang script now and I realized that if I had this information, I would be able to conditionally choose between downloading a pre-built binary of running the deno script.
- chore(deps): update dependency deno to v2.8.0 (#184)

This PR contains the following updates:

Package	Update	Change
deno	minor	`2.7.14` →
`2.8.0`

Release Notes

denoland/deno (deno)

v2.8.0

Compare
Source

Configuration

📅 Schedule: (in timezone America/Chicago)

Branch creation
- Only on Sunday and Saturday (* * * * 0,6)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update
again.

If you want to rebase/retry this PR, check
this box

This PR was generated by Mend Renovate.
View the repository job
log.

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
- ci: delete lockfile update workflow (#183)

follow-up to: #181 where we
just delete the file that was commented out. it's not needed anymore
after testing success without it.
- chore(deps): lock file maintenance (#182)

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency
versions.

Configuration

📅 Schedule: (in timezone America/Chicago)

Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get
config
help if
that's undesired.

If you want to rebase/retry this PR, check
this box

This PR was generated by Mend Renovate.
View the repository job
log.

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
- ci: disable deno frozen lock-file to make CI/renovatebot setup less complex (#181)

Problem

having frozen lock file has been really annoying, but especially because
of renovatebot.

even with frozen disabled, from my understanding, deno still uses lock
files. I dont have a lot of experience with the default deno behavior
where frozen is off but lock files are on. I want to try it out.

there is a new feature being added to renovatebot that allows you to
tell renovatebot to run '--frozen false' but I am not sure when it will
be launched. when it does, we could enable frozen in the deno.jsonc
again and still not need the github action for updating lock file.

Solution

disable frozen lock files from deno config so we use the default
behavior.

Testing

Added automated tests.
Manually tested. If you check this box, provide instructions for
others to test, too.

After merging this PR, I am going to run renovatebot to see if it
successfully updates some deno dependencies and also the lock file.

Notes for reviewers

- build: simplify AGENTS.md and reduce token usage running tests (#180)

Related GitHub Issues

Problem

AGENTS.md uses too many tokens.

when you run tests, it adds the entire stdout to context.
I tend to use very small and simple files with less stuff in it.
let's try deleting a ton of the content.

Solution

tell agent to use junit report for finding failures to fix
remove everything except commands to run.

Testing

Added automated tests.
Manually tested. If you check this box, provide instructions for
others to test, too.

Notes for reviewers

feat: shebang command provides information on what got cloned

4545650

I am writing a shebang script now and I realized that if I had this information, I would be able to conditionally choose between downloading a pre-built binary of running the deno script.

levibostian marked this pull request as ready for review May 24, 2026 12:13

levibostian merged commit 28185e0 into main May 24, 2026
11 checks passed

levibostian deleted the shebang-provide-env-vars branch May 24, 2026 12:13

Conversation

levibostian commented May 24, 2026

Related GitHub Issues

Problem

Solution

Testing

Notes for reviewers

Uh oh!

github-actions Bot commented May 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

decaf

Related GitHub Issues

Problem

Solution

Testing

Notes for reviewers

Release Notes

Configuration

Configuration

Problem

Solution

Testing

Notes for reviewers

Related GitHub Issues

Problem

Solution

Testing

Notes for reviewers

Release Notes

Configuration

Configuration

Problem

Solution

Testing

Notes for reviewers

Related GitHub Issues

Problem

Solution

Testing

Notes for reviewers

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

github-actions Bot commented May 24, 2026 •

edited

Loading