Skip to content

fix(ci): build the Maven extension jar outside the Socket Firewall shims #1390

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Jeppe Fredsgaard Blaabjerg (jfblaa) merged 3 commits into from
Jul 1, 2026
Merged

fix(ci): build the Maven extension jar outside the Socket Firewall shims #1390

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
59f7e2a
fix(ci): build the Maven extension jar outside the Socket Firewall shims
jfblaa Jul 1, 2026
6adfbb5
chore(ci): remove the unused maven-extension-jar workflow
jfblaa Jul 1, 2026
c0c8629
bump coana cli version
jfblaa Jul 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 0 additions & 46 deletions .github/workflows/maven-extension-jar.yml
View file
Open in desktop

This file was deleted.

12 changes: 8 additions & 4 deletions .github/workflows/provenance.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -206,15 +206,19 @@ jobs:

# Compile the Maven manifest extension jar so the dist build bundles it
# into dist/manifest-scripts (the jar is never committed; it ships only in
# the published package). The org action allowlist forbids actions/setup-java,
# so use a JDK pre-installed on the runner image (JAVA_HOME_17_X64), falling
# back to the runner's default `java`. build-jar.sh uses the Maven wrapper.
# the published package). Invoke build-jar.sh directly, NOT via `pnpm run`:
# Socket Firewall wraps the package managers (npm/pnpm/...) it shims, so a
# `pnpm run` would route the Maven wrapper's download through sfw, which
# fails on the non-package fetch. Running bash directly keeps the Maven
# download outside the shimmed process tree. The org action allowlist forbids
# actions/setup-java, so use a JDK pre-installed on the runner image
# (JAVA_HOME_17_X64), falling back to the runner's default `java`.
- name: Build Maven manifest extension jar
run: |
if [ -n "${JAVA_HOME_17_X64:-}" ]; then
export JAVA_HOME="$JAVA_HOME_17_X64"
fi
pnpm run build:maven-extension
bash src/commands/manifest/scripts/maven-extension/build-jar.sh

- run: INLINED_SOCKET_CLI_PUBLISHED_BUILD=1 pnpm run build:dist
- name: Publish socket
Expand Down
Loading