Automatically update the website releases based on the Github Release status

[Stefterv]

Relevant sub-area for this feature?

Build process

Feature description

In theory we can add a Github Action to this repo that will trigger an update workflow on the processing-website repository

steps:
  - name: Trigger workflow
    uses: actions/github-script@v7
    with:
      github-token: ${{ secrets.PAT_TOKEN }}
      script: |
        await github.rest.actions.createWorkflowDispatch({
          owner: 'processing',
          repo: 'processing-website',
          workflow_id: 'release.yml',
          ref: 'main'
        })

Benefits

This would simplify the release process and remove an extra step

Possible challenges

It also creates more coupling between the two repositories than I am comfortable with...

Additional context

No response

[SableRaf]

It also creates more coupling between the two repositories than I am comfortable with...

Feels like that coupling might be an acceptable trade-off for removing the need for manual updates. Are there alternatives that could still automate website updates while reducing the level of coupling?

[Stefterv]

processing/processing-website#589

Yes I noted an alternative here

[Stefterv]

Okay I did some digging and this is the current situation

processing-website

• Should update on new processing4 release
  • Update keywords.txt ?
  • Update releases
• Should update on processing-examples change
• Created a reference.zip in the past which was used by processing4
• Include processing-doclet
• Remove all the dynamic data from the repo as it is confusing for contributors what is editable

processing4-javadocs

• Should update with release
• Move into the processing4 repo

processing4

• Releases new updates
• Should have a reference.zip attached to the release
• Create a Github Action to generate the reference.zip with npm run zip in the processing-website repo
• Update the download url in processing to download the reference from e.g. https://github.com/processing/processing4/releases/processing-1294-4.3.1/download/release.zip
  • On caveat in this is that the tag name is not available in the Java code currently
• Chore: Base.java should be auto-updated based on the current version
• Should trigger processing-website updates
• Should trigger processing4-javadoc updates

processing-contributions-legacy

• Updates continuously
• Publishes said updates to elle.processing.org
• Deprecate and replace with processing-contributions
• Make processing-contributions public

processing-examples

• Updates continuously
• Gets pulled into processing4 automatically and processing-website by hand
• Question, why is this a seperate repository?
• Should trigger processing-website updates

processing-doclet

• Should update on new release
• Generates files for the processing website
• Should be moved into the processing-website and managed with a Github Action

processing-download

• Deprecated: Needs to life on since it is used by Processing3 which I tested today and cannot easily release new versions for see Stefterv/processing
• Referenced by processing and processing4 for its /contribs
• Referenced by the io library for its reference.zip
• Find a nice way to deprecate

[Stefterv]

Let's set this all up in one go and after #888