Skip to content

fix: use app-key and fuelup-env for publishing last version metadata #719

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.

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
merged 1 commit into from
Apr 7, 2025

Conversation

kayagokalp
Copy link
Member

closes #718.

I realized we used to have a similar issue for other stuff in gh-pages. #700 and #701 is merged to fix that. This PR brings the fuelup env and key generation steps to publishing the metadata as well.

@kayagokalp kayagokalp self-assigned this Apr 7, 2025
@kayagokalp kayagokalp added bug Something isn't working ci labels Apr 7, 2025
@kayagokalp kayagokalp requested a review from a team April 7, 2025 18:24
@kayagokalp kayagokalp enabled auto-merge (squash) April 7, 2025 18:24
Copy link
Contributor

github-actions bot commented Apr 7, 2025

LCOV of commit 58ae895 during CI #2155

Summary coverage rate:
  lines......: 85.6% (2384 of 2784 lines)
  functions..: 54.0% (334 of 619 functions)
  branches...: 63.0% (290 of 460 branches)

Files changed coverage rate: n/a

@kayagokalp kayagokalp merged commit 60d36d7 into master Apr 7, 2025
18 checks passed
@kayagokalp kayagokalp deleted the kayagokalp/718 branch April 7, 2025 22:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ci
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ci: CI cannot push to gh-pages without a pull request for publishing fuelup version
2 participants