Skip to content

Claude/build failure qnalvi #4

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

Closed
profradha wants to merge 2 commits into from
Closed

Claude/build failure qnalvi #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1b77234
Generate and verify C2PA Content Credentials in the browser
claude Aug 25, 2026
1546a53
Decode BMPString with as_chunks to satisfy clippy
claude Aug 26, 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
13 changes: 13 additions & 0 deletions .github/workflows/deploy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,8 +53,21 @@ jobs:
- name: Install dependencies
run: npm ci

# The signing credentials for Content Credentials. When both secrets are
# set, `crates/imagecore/build.rs` compiles them into the engine instead
# of the demo key committed under `signing/`; when they are absent, as on
# a fork, the demo key is used and the build still works.
#
# To be clear about what this buys: a secret keeps a key out of public git
# history. It cannot make the key secret. This engine is served to
# browsers, so whichever key it carries is published along with it. See
# `signing/README.md` for why that is inherent to client-side signing and
# what a trustworthy setup would look like instead.
- name: Build
run: npm run build
env:
C2PA_SIGNING_CERT: ${{ secrets.C2PA_SIGNING_CERT }}
C2PA_SIGNING_KEY: ${{ secrets.C2PA_SIGNING_KEY }}

- name: Setup Pages
uses: actions/configure-pages@v5
Expand Down
Loading
Loading