V3.0.1

Nothing changed in the action workflow, just cleaned up the repo a bit and dropped stuff that's not necessary anymore.

What's Changed

• Cleanup For Release by @HarrierPigeon in #13

Full Changelog: v3.0.0...v3.0.1

v3.0.0: Drop Node12, Make Publishable

Big changes: As of this time, everything this action uses is up to date and should stay that way for a long while.

We're now using our own thing to update the clasp token we store in Actions Secrets. This means that we're now in control of our own destiny a little more, and don't have to worry about other people not updating stuff.

Updating org secrets is now a fully supported option, as well, which means that you only need to maintain one CLASP token if you have multiple projects owned / edited by the same Google account.

Also, with the overhaul, this is now fully capable of being used like a normal Github Action would be, Here's a fairly simple example:

    - name: Send Codebase To AppsScript
      uses: texas-mcallen-mission/deploy-google-app-script-action-typescript/@v3.0.0
      with:
        CLASP_TOKEN_VALUE: ${{ secrets.CLASPRC_JSON }}
        CLASP_TOKEN_NAME: 'CLASPRC_JSON'
        REPO_ACCESS_TOKEN: ${{ secrets.REPO_ACCESS_TOKEN }}
        SCRIPT_ID: ${{ secrets.SCRIPT_ID_DEV }}
        PARENT_ID: ${{ secrets.PARENT_ID_DEV }} # optional.
        DEPLOYMENT_ID: ${{ secrets.DEPLOYMENT_ID }} # optional.
        CONFIG_DATA: ${{ secrets.CONFIG_DATA }} # optional.

What's Changed

• Backend Improvements by @HarrierPigeon in #9
• Remove Deprecated Dependencies, Proper Org Secret Support, Publishable Action Completed by @HarrierPigeon in #12

Full Changelog: v2.3.0...v3.0.0

V2.4.0: Error Collection, QoL

With this release, it's a lot easier to get started with this CI workflow- almost all the fancy files you need are taken care of now behind-the-scenes, though we would recommend you make local versions, especially if you plan on doing stuff like adding macros.

Error collection and analysis (AKA the workflow not getting a green circle when it shouldn't) is a thing now- the only way that you'll see a green checkmark now is if your code has pushed.

For a demonstration, see the deploy-tester repo!

What's Changed

• Backend Improvements by @HarrierPigeon in #9

Full Changelog: v2.3.0...v2.4.0

V2.3.0: Now includes git submodules

Repository submodules are now pulled in automatically when this is run- this became necessary when sheetCore broke off of the key indicator system.

What's Changed

• Update reusable.yml by @HarrierPigeon in #7

Full Changelog: v2.2.0...v2.3.0

v2.3.0 - include git submodules

Minor change, should let me use submodules in the key indicator system with CI.

v2.2.0 - Config Passthrough now optional, script loading works now

v2.2.0 - Self-Contained Workflow

reusable.yml has been updated to pull in the code from this repository, so that it doesn't have to be done manually.

What's Changed

• Running Python workflows now works on external repositories by @HarrierPigeon in #6

Full Changelog: v2.1.0...v2.2.0

v2.1.0

Version 2.1.0 - Config Data Pass-through

Since the release of v2.0.0, we noticed that config files weren't actually working as intended- the final git-info.js information was completely missing. Now, the reusable workflow stub works perfectly with the big action workflow- using the same method described in the last release.

What's Changed

• Setting config data in actions actually works now! by @HarrierPigeon in #4

Full Changelog: V2.0.0...v2.1.0

Version 2.0- Reusable data flow!

Version 2.0

This release adds the ability to reuse the main action workflow by making copies of a reusable stub. This is in line with the vision of making it as easy as possible to have & maintain multiple deployments without needing to manage configuration pages and such across versions.

All the secrets that you need to change are now in one easy-to-access location with everything else hiding in the background, as well! Simply change the references in reusable-stubby.yml.

      CLASPRC_JSON: ${{ secrets.CLASPRC_JSON }}
      REPO_ACCESS_TOKEN: ${{ secrets.REPO_ACCESS_TOKEN }}
      DEPLOYMENT_ID: ${{ secrets.DEPLOYMENT_ID }}
      SCRIPT_ID: ${{secrets.SCRIPT_ID}}
      PARENT_ID: ${{secrets.PARENT_ID}}
      CONFIG_DATA: ${{ secrets.CONFIG_JSON }}

BREAKING CHANGES

you need to have a copy of git-info.js in your root directory at present. This may be updated in the future.

What's Changed

• Conversion to reusable action flow! by @HarrierPigeon in #2
• Final pre-update push by @HarrierPigeon in #3

Full Changelog: v1.1.0...V2.0.0

Version 1.1.0 - New Config File Options!

This update is more specifically for the key indicator system.

Why Is This Important?

This will let you stick sensitive bits of config data into GitHub's action secrets instead of having it publicly available. This is useful for two reasons:

1. It's a lot more secure! You won't have to leak document ID's out to the world with your published-everywhere version, meaning that your live release stuff could live in a public repository.
2. It's now easier to maintain development versions, and have multiple configurations pre-set and ready to go

• All that you need to do to create multiple environments is basically duplicate the workflow, add some more secrets with similar data (IE a secret named TEST_INSTANCE_2_SCRIPT_ID) and change the references to the workflow branches to use the new thing.

What's Changed

• update workflow to add configuration files to secrets by @HarrierPigeon in #1

New Contributors

• @HarrierPigeon made their first contribution in #1

Full Changelog: v1.0.0...v1.1.0

Version 1

This version has everything you need to get going with typescript on gas via github!