Weird site build failures ?

[ekrimmel]

The Jekyll site is not building as expected. See Actions log. Yesterday I merged a pull request from Alex, which triggered a build and that build failed at the time. I poked around and made some other edits that didn't "fix" anything, but then the site did build, but then the scheduled run failed. I don't understand enough to know if there's a real problem, or things just aren't going quite as I expect...

[adamancer]

This issue affects all forks. The requests to Zenodo are triggering an error due to a new rate limit put in place over there last month (https://blog.zenodo.org/2025/11/25/2025-11-14-search-api-updates/).

[adamancer]

I can't get resolving the Zenodo DOIs work in the action. I've tried adding an authorization token, but the responses from Zenodo seem to be ignoring it, and I wonder if they're not just rejecting all traffic from GitHub Actions.

The code itself is fine, and I've implemented a workaround on my dev repo which simply updates the Zenodo resources locally prior to upload. The major disadvantage to that is that it requires the build script to be run prior to upload but I don't see another option currently. Should I push it?

[ekrimmel]

Ehhhhh.... For the workaround on your fork, when you say prior to upload does that mean locally? If so, I think let's hold off on pushing for now. This isn't a wildfire issue since I don't anticipate content edits to the site over the holidays, and I think it may be a no-go for the site to need to run a local process prior to building on GitHub Pages.

[ekrimmel]

Closing for now as the issue seems to have resolved itself from the Zenodo side of things...

[ekrimmel]

@adamancer, I think our Zenodo issue is back :( :( :(

See build failure on @alexpaleo's branch (https://github.com/alexpaleo/paleo-data.github.io/actions/runs/21175449690/job/60902935377). This issues affects #148.

[adamancer]

I've made some changes to my fork to address this, including adding an API token to the Zenodo requests and caching responses as part of the site build. The token seems to be working, but we'll need to keep an eye on it in case I just got lucky.

I'll push those over here next week and add instructions about adding a Zenodo token to forks.

[alexpaleo]

Thank you!

[alexpaleo]

Hi! Sorry, something is happening again with my fork when I was trying to update the HH page. 🫤

[adamancer]

The error on your fork is from invalid YAML in the happy hour file. Try adding quotes to the title of the first entry:

- title: "Digitizing collections from Nilpena Ediacara National Park: a case study"
  date: 2026-05-07
  topics: [data wrangling, workflow]
  notes: https://docs.google.com/document/d/18cdnl76zuu1ebCaT1MhR2ChEHKD8zQILra2bqWvepnY/edit?usp=sharing
  recording: 

YAML uses colons to separate keys and values, so typically you need to put quotes around values that contain a colon. Values that do not also contain a space (like a URL) are an exception to this rule and do not need to be quoted.