Skip to content

v1.4.2

Latest
Compare
Choose a tag to compare
@github-actions github-actions released this 25 Oct 08:13
Restore verbosity, update insecure dependencies @Nuru (#108) ## what
  • Restore test verbosity inadvertently disabled in #87
  • Consolidate Dependabot PRs
  • Add dependabot.yml

why

  • Restore normal behavior
  • Consolidate PRs
  • Group go security updates, since they only affect testing and are usually not exploitable here, to reduce the number of PRs to review

references

🐛 Bug Fixes

fix(synthetics): Adjust timeframes loop to include child objects @elx-bob (#107) ## what
  • Change loop to use child objects instead of timeframes object.
  • Update Datadog provider requirements for synthetics
  • Fix broken test

why

  • Synthetics options.scheduling.timeframes was incorrectly treated as an object, and is now correctly treated as a list of objects, as specified in the API documentation
  • Improved API validation at the server level uncovered a bug in the Datadog provider for synthetic tests, which was fixed in provider v3.43.1
  • The test requirement that the monitor had no tags was overly strict, requiring a nil output rather than an empty one, causing properly working code to be marked as failing

references

🤖 Automatic Updates

Migrate new test account @osterman (#106) ## what - Update `.github/settings.yml` - Update `.github/chatops.yml` files

why

  • Re-apply .github/settings.yml from org level to get terratest environment
  • Migrate to new test account

References

  • DEV-388 Automate clean up of test account in new organization
  • DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
  • DEV-386 Update terratest to use new testing account with GitHub OIDC
Update .github/settings.yml @osterman (#101) ## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

  • Re-apply .github/settings.yml from org level
  • Use organization level auto-release settings

references

  • DEV-1242 Add protected tags with Repository Rulesets on GitHub
Update .github/settings.yml @osterman (#99) ## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

  • Re-apply .github/settings.yml from org level
  • Use organization level auto-release settings

references

  • DEV-1242 Add protected tags with Repository Rulesets on GitHub
Update release workflow to allow pull-requests: write @osterman (#98) ## what - Update workflow (`.github/workflows/release.yaml`) to have permission to comment on PR

why

  • So we can support commenting on PRs with a link to the release
Update GitHub Workflows to use shared workflows from '.github' repo @osterman (#97) ## what - Update workflows (`.github/workflows`) to use shared workflows from `.github` repo

why

  • Reduce nested levels of reusable workflows
Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#96) ## what - Update workflows (`.github/workflows`) to add `issue: write` permission needed by ReviewDog `tflint` action

why

  • The ReviewDog action will comment with line-level suggestions based on linting failures
Update GitHub workflows @osterman (#95) ## what - Update workflows (`.github/workflows/settings.yaml`)

why

  • Support new readme generation workflow.
  • Generate banners
Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#94) ## what
  • Install latest GitHub Action Workflows

why

  • Use shared workflows from cldouposse/.github repository
  • Simplify management of workflows from centralized hub of configuration
Add GitHub Settings @osterman (#93) ## what - Install a repository config (`.github/settings.yaml`)

why

  • Programmatically manage GitHub repo settings
Update README.md and docs @cloudpossebot (#91) ## what This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

Update Scaffolding @osterman (#92) ## what - Reran `make readme` to rebuild `README.md` from `README.yaml` - Migrate to square badges - Add scaffolding for repo settings and Mergify

why

  • Upstream template changed in the .github repo
  • Work better with repository rulesets
  • Modernize look & feel