Skip to content

🐛 remove banned triple slash#1121

Merged
cowboyd merged 1 commit into
v4from
fix-banned-triple-slash
Feb 19, 2026
Merged

🐛 remove banned triple slash#1121
cowboyd merged 1 commit into
v4from
fix-banned-triple-slash

Conversation

@cowboyd

@cowboyd cowboyd commented Feb 19, 2026

Copy link
Copy Markdown
Member

Motivation

jsr.io does not allow triple slashes.

Approach

This remove it since it can be set by the consuming library. This also adds validation checks after tests have successfully run to see if publication would succeed on both npm and jsr.

image

This also adds these same pre-flight checks to the actual publication workflow. It ensures that both JSR and NPM will work before attempting either. That way we don't end up in a situation where we have the package on one registry and not another.

@pkg-pr-new

pkg-pr-new Bot commented Feb 19, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/thefrontside/effection@1121

commit: 346be14

JSR does not allow triple slashes, and so this was causing
publication to fail.

This removes it since it does not actually add anything of value.
Furthermore, it adds npm and jsr dry runs after tests run.

Finally, it adds these preflight checks to the publication workflow as
a precondition for _both_ npm _and_ jsr. That way, we won't publish
either unless both are expected to work.
@cowboyd cowboyd merged commit 299b5be into v4 Feb 19, 2026
17 checks passed
@cowboyd cowboyd deleted the fix-banned-triple-slash branch February 19, 2026 16:47
node-version: 24

- name: Build NPM
run: deno task build:npm 4.0.0-verify.0

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is there a hardcoded version here?

node-version: 24

- name: Build NPM
run: deno task build:npm 4.0.0-verify.0

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, i see because you need a version number. It might be worth adding a comment here to explain.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, this is just a total dummy number. It could be 12.1000.675-verify.0

@cowboyd cowboyd mentioned this pull request Jul 8, 2026
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.

2 participants