Skip to content

feat(wasm-privacy-coin): wasm java packaging#293

Draft
Ranjna-G wants to merge 1 commit into
masterfrom
wasm-java-packaging
Draft

feat(wasm-privacy-coin): wasm java packaging#293
Ranjna-G wants to merge 1 commit into
masterfrom
wasm-java-packaging

Conversation

@Ranjna-G

Copy link
Copy Markdown

Ticket: CSHLD: 784

uses: actions/download-artifact@v4
with:
name: wasm-privacy-coin-build
path: packages/wasm-privacy-coin/dist/

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The JAR ends up double-nested here — v4 extracts artifact paths relative to this destination, so it lands at dist/packages/wasm-privacy-coin/dist/wasm-privacy-coin.jar instead of where the deploy step looks. Change to path: packages/wasm-privacy-coin/ (or drop the path entirely and adjust -Dfile accordingly).

with:
name: wasm-privacy-coin-build
path: |
packages/wasm-privacy-coin/pkg/

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

pkg/ is wasm-pack output and won't exist here since this package has needs-wasm-pack: false. Safe to remove this path.


<groupId>com.bitgo</groupId>
<artifactId>wasm-privacy-coin</artifactId>
<version>0.1.0</version>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This version is read statically so every master merge will attempt to publish 0.1.0 — CodeArtifact release repos reject re-publishing an existing version. Worth wiring into multi-semantic-release output (same pattern as grpc-protobufs) or adding a version-change gate.

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