• 1.10.0 - 2019-03-31
  

  Testing!

  This release improves the CLI scaffold template with a new file: index.test.js. It outlines a pattern for testing GItHub Actions with actions-toolkit, leveraging Toolkit.run. Try it out with:

  npx actions-toolkit <folder>
  

  I'll be sharing some docs on this soon!

  What’s Changed

  • Fix publish workflow (#72) @ JasonEtco
  • Include test file in CLI scaffold (#73) @ JasonEtco
• 1.9.1 - 2019-03-29
  

  What’s Changed

  • Fix missing methods on tools.log (#69) @ JasonEtco
  • Remove GITHUB_REF and GITHUB_TOKEN from required env vars (#71) @ JasonEtco
• 1.9.0 - 2019-03-27
  

  New feature

  This release introduces the secrets option. If present, the Action will exit and fail if required secrets have not been set. Here's an example:

  action "My action" {
    uses = "JasonEtco/secrets@master"
    secrets = ["API_KEY"]
  }

  // This will fail because `API_SECRET` wasn't passed!
  new Toolkit({ secrets: ['API_KEY', 'API_SECRET'] })

  Check out #66 for all the details ✨

  What’s Changed

  • Add secrets option (#66) @ JasonEtco
• 1.8.1 - 2019-03-27
  

  What’s Changed

  • Support non-async functions in Toolkit.run (#67) @ JasonEtco
• 1.8.0 - 2019-03-27
  

  New feature

  In #63, @ jclem added a new static method to the Toolkit class: #run. It takes a function argument and runs that function, as a way of enabling easier async/await patterns and modularity. Check it out!

  const { Toolkit } = require('actions-toolkit')

  Toolkit.run(async tools => {
  tools.log.success('We did it team!')
  })

  What’s Changed

  • Use logger in exit (#64) @ JasonEtco
  • Add Toolkit.run (#63) @ jclem
• 1.7.0 - 2019-03-23
  

  Enhanced CLI

  This release introduces a wonderfully enhanced CLI tool for creating a new GitHub Action, courtesy of @ macklinu. Check out #57 for the full details ✨ You can run it through npx:

  npx actions-toolkit my-action
  

  What’s Changed

  • Use logger in exit (#64) @ JasonEtco
  • Create CLI questionnaire (#57) @ macklinu
• 1.6.0 - 2019-03-16
  

  New feature

  This release introduces Toolkit#command, a new method that will run the provided function when a matching slash-command is found. From the README:

  Respond to a slash-command posted in a GitHub issue, comment, pull request, pull request review or commit comment. Arguments to the slash command are parsed by minimist. You can use a slash command in a larger comment, but the command must be at the start of the line:

  Hey, let's deploy this!
  /deploy --app example --container node:alpine
  

  tools.command('deploy', async (args: ParsedArgs, match: RegExpExecArray) => {
    console.log(args)
    // -> { app: 'example', container: 'node:alpine' }
  })

  What’s Changed

  • Slash commands (#53) @ JasonEtco

• c727adb 1.10.0
• 5ed87f0 Merge pull request #73 from JasonEtco/testing-setup
• 8f8c3ec Need to actually require our entrypoint
• cc40024 Add npm scripts
• 28a29fb Add index.test.js to README
• c5317c7 Add index.test.js file
• 39c8f45 Update template again
• afe1171 Update snapshots, include Jest in package.json
• 799eacf Improve the index.js file
• 10f060e Rename the entrypoint to index.js
• 1d9343a Merge pull request #72 from JasonEtco/fix-publish-workflow
• 5c5b437 Hopefully fix the publish action for realsies
• 428bacf Remove prepare script
• 5340f4f Correct publish action's tag file path
• d497ce1 1.9.1
• f22f54d Merge pull request #71 from JasonEtco/dont-warn-optional-env-vars
• ec23cfc Merge branch 'master' into dont-warn-optional-env-vars
• a13e036 Merge pull request #69 from JasonEtco/fix-log-disable
• 4f6302f Remove GITHUB_REF and GITHUB_TOKEN from required env vars
• d9d8290 Improve types
• 1bd0fc3 More methods to type
• 267f2b6 Update Signale and @ types/signale
• 85a8817 Add comments, prefer `logger` as prototype
• e215b28 Object.setPrototypeOf is black magic

Compare