https://github.com/tidev/titanium-builds-regen-action

Regenerates Titanium SDK releases, branches, and branch builds
https://github.com/tidev/titanium-builds-regen-action

Last synced: about 1 month ago
JSON representation

Regenerates Titanium SDK releases, branches, and branch builds

• Host: GitHub
• URL: https://github.com/tidev/titanium-builds-regen-action
• Owner: tidev
• License: apache-2.0
• Created: 2022-06-09T22:53:01.000Z (about 3 years ago)
• Default Branch: main
• Last Pushed: 2024-02-12T17:53:34.000Z (over 1 year ago)
• Last Synced: 2024-12-01T07:10:50.159Z (7 months ago)
• Language: JavaScript
• Size: 1.26 MB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Funding: .github/FUNDING.yml
  • License: LICENSE

Awesome Lists containing this project

README

        
# Titanium SDK Builds Regen Action

This action can be used in GitHub workflows to generate static JSON files

containing Titanium SDK releases, branches, and branch builds.

## Usage

In your project repo, create the file: `.github/workflows/regen-builds.yml`

```yaml

name: 'Regen Builds'

on:

  workflow_dispatch:

  repository_dispatch:

    types: [ regen-builds ]

jobs:

  regen:

    runs-on: ubuntu-latest

    steps:

      # third-party action that cancels previous runs

      - name: Cancel Previous Runs

        uses: styfle/[email protected]

        with:

          access_token: ${{ github.token }}

      - name: Checkout titanium-builds

        uses: actions/checkout@v3

      - name: Retrieve the builds

        uses: tidev/titanium-builds-regen-action@v1

        with:

          output-dir: 'public/registry'

          repo-token: ${{ secrets.GITHUB_TOKEN }}

      - name: Commit changes

        id: committed

        uses: stefanzweifel/git-auto-commit-action@v4

      - name: Repository Dispatch

        if: steps.committed.outputs.changes_detected == 'true'

        uses: peter-evans/repository-dispatch@v2

        with:

          event-type: deploy

          token: ${{ secrets.REGEN_BUILDS_DOCS_GITHUB_TOKEN }}

```

## Releasing a new version

To release a new version we need to bump the version and then recreate the `v1`

tag. We use the `v1` tag to avoid having to update the action in all

repositories when a change is made. To do this:

1. Bump the version as required using `npm version major|minor|patch`

2. Recreate the v1 tag using `git tag --force v1`

3. Delete the tag on the remote `git tag :refs/tags/v1`

4. Push the commit and updated tags `git push -f --tags`

## Manual Run

```sh

$ TOKEN= OUTPUT_DIR=registry node index.js

```