Skip to content

v1.537.0
Compare
Choose a tag to compare
@cloudposse-releaser cloudposse-releaser released this 06 Jun 13:34
· 2 commits to refs/heads/main since this release
v1.537.0
8031549
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

🤖 Automatic Updates

Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#30) ## 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

chore(deps): update terraform cloudposse/backup/aws to v1.0.3 @[renovate[bot]](https://github.com/apps/renovate) (#3) ## What * Update `terraform-aws-backup` to `1.03` * Change advanced_backup_setting.backup_options map(string)

Why

This PR contains the following updates:

Package Type Update Change
cloudposse/backup/aws (source) module patch 1.0.0 -> 1.0.3

Release Notes

cloudposse/terraform-aws-backup (cloudposse/backup/aws)

v1.0.3

Compare Source

Change advanced_backup_setting.backup_options map(string) @​cwallace-omg (#​96)

what

  • Change the variable advanced_backup_setting.backup_options from type string to type map(string).

why

If the advanced_backup_setting.backup_options variable is a string, this results in an error when planning or applying:

16:21:12.722 ERROR  terraform invocation failed in /tmp/terragrunt-cache/-FDnhxSQgd3gy3AJn3jI-TkIT9c/DzZH2oKvEUO4zTXgeTgdoazRmVw
16:21:12.722 ERROR  error occurred:

* Failed to execute "terraform plan" in /tmp/terragrunt-cache/-FDnhxSQgd3gy3AJn3jI-TkIT9c/DzZH2oKvEUO4zTXgeTgdoazRmVw
  ╷
  │ Error: Incorrect attribute value type
  │ 
  │   on main.tf line 93, in resource "aws_backup_plan" "default":
  │   93:       backup_options = var.advanced_backup_setting.backup_options
  │     ├────────────────
  │     │ var.advanced_backup_setting.backup_options is "{ WindowsVSS = \"enabled\" }"
  │ 
  │ Inappropriate value for attribute "backup_options": map of string required.
  ╵
  
  exit status 1

The provider helpfully suggests: Inappropriate value for attribute "backup_options": map of string required.. Making this change results in a successful plan.

references

The Example Usage demonstrates the use of a map for this parameter:
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/backup_plan#example-usage

🤖 Automatic Updates

Migrate new test account @​osterman (#​92)

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

v1.0.2

Compare Source

Support for additional policy for creating reserial copies of S3 buckets @​obervinov (#​89)

what

  • Added an additional policy (AWSBackupServiceRolePolicyForS3Backup) to the IAM user being created.
  • This allows the module to be used for creating backups of S3 buckets.

why

  • Backing up S3 buckets was a missing feature necessary to fully cover the backup process through AWS Backup using this module.
  • The IAM user created by this module lacked the additional AWSBackupServiceRolePolicyForS3Backup policy needed for S3 bucket backups.

references

🤖 Automatic Updates

Update .github/settings.yml @​osterman (#​91)

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 (#​90)

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

v1.0.1

Compare Source

fix: null value reference when copy_action is specified without lifecycle options @​carlosaml (#​86)

what

Attempt to get attribute from null value error when a copy_action is specified in a backup rule without any lifecycle options

steps to reproduce

Based on the complete example:


module "backup" {
  source = "../.."

  backup_resources = [module.efs.arn]
  not_resources    = var.not_resources

  rules = [
    {
      name              = "${module.this.name}-daily"
      schedule          = var.schedule
      start_window      = var.start_window
      completion_window = var.completion_window
      lifecycle = {
        cold_storage_after = var.cold_storage_after
        delete_after       = var.delete_after
      }
      copy_action = {
        destination_vault_arn = "arn:aws:backup:us-east-2:123456789000:backup-vault:my-vault"
      }
    }
  ]

  backup_vault_lock_configuration = {
    max_retention_days = 365
    min_retention_days = 30
  }

  context = module.this.context
}

why

The following error should not happen:

╷
│ Error: Attempt to get attribute from null value
│
│   on ../../main.tf line 79, in resource "aws_backup_plan" "default":
│   79:               cold_storage_after = rule.value.copy_action.lifecycle.cold_storage_after
│     ├────────────────
│     │ rule.value.copy_action.lifecycle is null
│
│ This value is null, so it does not have any attributes.
╵
╷
│ Error: Attempt to get attribute from null value
│
│   on ../../main.tf line 80, in resource "aws_backup_plan" "default":
│   80:               delete_after       = rule.value.copy_action.lifecycle.delete_after
│     ├────────────────
│     │ rule.value.copy_action.lifecycle is null
│
│ This value is null, so it does not have any attributes.
╵

🚀 Enhancements

chore(deps): update terraform cloudposse/dynamic-subnets/aws to v2.4.2 @​renovate (#​70)

This PR contains the following updates:

Package Type Update Change
cloudposse/dynamic-subnets/aws (source) module patch 2.4.1 -> 2.4.2
Release Notes
cloudposse/terraform-aws-dynamic-subnets (cloudposse/dynamic-subnets/aws)
v2.4.2

Compare Source

🚀 Enhancements
chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @​&#​8203;renovate (#&#​8203;191)

This PR contains the following updates:

Package Type Update Change
cloudposse/utils/aws (source) module minor 1.3.0 -> 1.4.0
Release Notes
cloudposse/terraform-aws-utils (cloudposse/utils/aws)
v1.4.0

Compare Source

Add il-central-1 region @​&#​8203;&#&#​8203;8203;jasonmk (#&#&#​8203;8203;31)
what

Add new Tel Aviv (il-central-1) region

why

Provide full coverage

references
Sync github @​&#​8203;&#&#​8203;8203;max-lobur (#&#&#​8203;8203;27)

Rebuild github dir from the template

🤖 Automatic Updates
chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @​&#​8203;renovate (#&#​8203;191)

This PR contains the following updates:

Package Type Update Change
cloudposse/utils/aws (source) module minor 1.3.0 -> 1.4.0
Release Notes
cloudposse/terraform-aws-utils (cloudposse/utils/aws)
v1.4.0

Compare Source

Add il-central-1 region @​&#​8203;&#&#​8203;8203;jasonmk (#&#&#​8203;8203;31)
what

Add new Tel Aviv (il-central-1) region

why

Provide full coverage

references
Sync github @​&#​8203;&#&#​8203;8203;max-lobur (#&#&#​8203;8203;27)

Rebuild github dir from the template

Update README.md and docs @​&#​8203;cloudpossebot (#&#​8203;189)
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

🤖 Automatic Updates

chore(deps): update terraform cloudposse/dynamic-subnets/aws to v2.4.2 @​renovate (#​70)

This PR contains the following updates:

Package Type Update Change
cloudposse/dynamic-subnets/aws (source) module patch 2.4.1 -> 2.4.2
Release Notes
cloudposse/terraform-aws-dynamic-subnets (cloudposse/dynamic-subnets/aws)
v2.4.2

Compare Source

🚀 Enhancements
chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @​&#​8203;renovate (#&#​8203;191)

This PR contains the following updates:

Package Type Update Change
cloudposse/utils/aws (source) module minor 1.3.0 -> 1.4.0
Release Notes
cloudposse/terraform-aws-utils (cloudposse/utils/aws)
v1.4.0

Compare Source

Add il-central-1 region @​&#​8203;&#&#​8203;8203;jasonmk (#&#&#​8203;8203;31)
what

Add new Tel Aviv (il-central-1) region

why

Provide full coverage

references
Sync github @​&#​8203;&#&#​8203;8203;max-lobur (#&#&#​8203;8203;27)

Rebuild github dir from the template

🤖 Automatic Updates
chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @​&#​8203;renovate (#&#​8203;191)

This PR contains the following updates:

Package Type Update Change
cloudposse/utils/aws (source) module minor 1.3.0 -> 1.4.0
Release Notes
cloudposse/terraform-aws-utils (cloudposse/utils/aws)
v1.4.0

Compare Source

Add il-central-1 region @​&#​8203;&#&#​8203;8203;jasonmk (#&#&#​8203;8203;31)
what

Add new Tel Aviv (il-central-1) region

why

Provide full coverage

references
Sync github @​&#​8203;&#&#​8203;8203;max-lobur (#&#&#​8203;8203;27)

Rebuild github dir from the template

Update README.md and docs @​&#​8203;cloudpossebot (#&#​8203;189)
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 release workflow to allow pull-requests: write @​osterman (#​84)

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
chore(deps): update terraform cloudposse/efs/aws to v1 @​renovate (#​68)

This PR contains the following updates:

Package Type Update Change
cloudposse/efs/aws (source) module major 0.36.0 -> 1.1.0
Release Notes
cloudposse/terraform-aws-efs (cloudposse/efs/aws)
v1.1.0

Compare Source

Make allow_all_egress a variable @​&#​8203;dlacosteGFM (#&#​8203;126)
What changes in this PR?
  • Default change is nothing (with this PR applied, nobody would have to change anything)
  • Makes a new parameter allow_all_egress which defaults to false
  • When creating the security group for the EFS volume, this line makes the security-group have an "allow egress to 0.0.0.0/0" rule entry. This PR makes that a configurable parameter instead
Why make this change?
  • EFS doesn't actually do egress, so this really makes no impact difference at all
  • ...but during a security audit we have a dangling "why do you allow egress to 0.0.0.0/0 on this?" question with no really good answer (so let's get rid of it as it doesn't do anything anyways)
References
  • PCI DSS 3.2.1 rule 1.1.7 - Requirement to review firewall and router rule sets every 6 months
  • PCI DSS 3.2.1 rule 1.2.1 - Restrict inbound and outbound traffic to that which is necessary for the environment
v1.0.0

Compare Source

🤖 Automatic Updates
chore(deps): update terraform cloudposse/security-group/aws to v2 (main) @​&#​8203;renovate (#&#​8203;135)

This PR contains the following updates:

Package Type Update Change
cloudposse/security-group/aws (source) module major 1.0.1 -> 2.2.0
Release Notes
cloudposse/terraform-aws-security-group (cloudposse/security-group/aws)
v2.2.0

Compare Source

`.editorconfig` Typo @​&#​8203;&#&#​8203;8203;milldr (#&#&#​8203;8203;50)
what

fixed intent typo

why

should be spelled "indent"

references

https://cloudposse.slack.com/archives/C01EY65H1PA/p1685638634845009

Sync github @​&#​8203;&#&#​8203;8203;max-lobur (#&#&#​8203;8203;47)

Rebuild github dir from the template

v2.1.0

Compare Source

  • No changes
v2.0.1

Compare Source

🐛 Bug Fixes
Properly handle enabled = false @​&#​8203;&#&#​8203;8203;Nuru (#&#&#​8203;8203;45)
what
  • Properly handle enabled = false
why
  • Fixes #​43
v2.0.0: Breaking changes

Compare Source

For details about migrating from v1 to v2, read the migration documentation.

Version 1 of this module had a flaw in that it tried to create new security group rules before deleting the old ones, which the Terraform provider does not handle properly and caused most attempted changes to fail. Version 2 resolves this issue by also creating a new security group when the rules change, installing the new rules in the new security group, then changing the security group assignments. Read the README and the migration documentation for more details.

Document migration from v1 to v2 @​&#​8203;&#&#​8203;8203;Nuru (#&#&#​8203;8203;42)
what
  • Document migration from v1 to v2 of this module
  • Fix #​40
why
  • Serious issues exist in v1, causing v2 to have different defaults and new settings. Documentation is needed to guide users on how to upgrade while minimizing service interruptions.
references
Fixes the link for examples/complete/main.tf @​&#​8203;&#&#​8203;8203;jdmedeiros (#&#&#​8203;8203;41)

Fixes the link for examples/complete/main.tf on the README.md file.

Update GitHub Workflows to use shared workflows from '.github' repo @​osterman (#​82)

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 (#​81)

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 (#​80)

what

  • Update workflows (.github/workflows/settings.yaml)

why

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

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 (#​74)

what

  • Install a repository config (.github/settings.yaml)

why

  • Programmatically manage GitHub repo settings
Update Scaffolding @​osterman (#​72)

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
Update README.md and docs @​cloudpossebot (#​71)

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 (#​69)

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
Update Terraform cloudposse/efs/aws to v0.36.0 @​renovate (#​66)

This PR contains the following updates:

Package Type Update Change
cloudposse/efs/aws (source) module minor 0.35.0 -> 0.36.0
Release Notes
cloudposse/terraform-aws-efs (cloudposse/efs/aws)
v0.36.0

Compare Source

🤖 Automatic Updates
chore(deps): update terraform cloudposse/route53-cluster-hostname/aws to v0.13.0 (main) @​&#​8203;renovate (#&#​8203;136)

This PR contains the following updates:

Package Type Update Change
cloudposse/route53-cluster-hostname/aws (source) module minor 0.12.2 -> 0.13.0
Release Notes
cloudposse/terraform-aws-route53-cluster-hostname (cloudposse/route53-cluster-hostname/aws)
v0.13.0

Compare Source

  • No changes
v0.12.3

Compare Source

Add zone inputs, update tests, add usage @​&#​8203;&#&#​8203;8203;nitrocode (#&#&#​8203;8203;42)
what
  • Add zone inputs, update tests, add usage
why
  • Verify zone name exists
  • Dynamically retrieve zone name based on data source inputs
references
git.io->cloudposse.tools update @​&#​8203;&#&#​8203;8203;dylanbannon (#&#&#​8203;8203;40)
what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References
  • DEV-143
Update README.md and docs @​&#​8203;cloudpossebot (#&#​8203;131)
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 Terraform cloudposse/vpc/aws to v2.2.0 @​renovate (#​67)

This PR contains the following updates:

Package Type Update Change
cloudposse/vpc/aws (source) module minor 2.1.1 -> 2.2.0
Release Notes
cloudposse/terraform-aws-vpc (cloudposse/vpc/aws)
v2.2.0

Compare Source

Update README.md and docs @​cloudpossebot (#​65)

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 README.md and docs @​cloudpossebot (#​64)

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 Terraform cloudposse/dynamic-subnets/aws to v2.4.1 @​renovate (#​62)

This PR contains the following updates:

Package Type Update Change
cloudposse/dynamic-subnets/aws (source) module minor 2.3.0 -> 2.4.1
Release Notes
cloudposse/terraform-aws-dynamic-subnets (cloudposse/dynamic-subnets/aws)
v2.4.1

Compare Source

🚀 Enhancements
Add subnet ARNs to outputs @​&#​8203;Nuru (#&#​8203;188)
what
  • Add subnet ARNs to outputs
why
v2.4.0

Compare Source

Update dependencies, remove deprecation, add NACL example @​&#​8203;Nuru (#&#​8203;184)
Note
Dropping support for deprecated EC2-Classic

With this release, EIPs allocated for NAT ingress are allocated in the default domain. This most likely does not affect you, but for accounts created before 2013-12-04 (almost 10 years ago as of this writing), the default domain could be EC2-Classic rather than the current VPC. Previously this module forced the EIPs to be in the VPC domain, but the breaking changes between AWS Provider v4 and v5 make that difficult.

If you find yourself in the rare situation where the EIPs allocated by this module are in EC2-Classic but you want them in VPC, then create the EIPs outside of this module and supply them to this module via nat_elastic_ips.

Custom NACLs

This release includes an example (examples/nacls/) showing how to create custom NACLs in conjunction with this module. Note that by default, this module creates wide-open NACLs, and subnets can only have one NACL associated with them. If you try to add a NACL to a subnet without disabling the default NACLs, you may get a possibly confusing error like:

│ Error: creating EC2 Network ACL: creating EC2 Network ACL (acl-0376c5f12dd9d784d) Association: InvalidAssociationID.NotFound: The association ID 'aclassoc-0818d5a9e3876a2bb' does not exist

See https://github.com/hashicorp/terraform-provider-aws/issues/31888

what
  • Make appropriate inputs non-nullable (treat an input of null as meaning "default")
  • Remove aws_eip vpc = true
  • Update terraform cloudposse/utils/aws to v1.3.0 (Supersedes and closes #​182)
  • Add example of how to add custom NACLs to subnets created by this module (Supersedes and closes #​176)
  • Update tests and test framework
why
  • Allow better, more consistent configuration
  • Deprecated
  • Include support for new AWS regions
  • Encourage composition of modules and resources rather than aggregation of functionality into bloated modules (c.f. #​176)
  • Stay current with features, bug fixes, and security updates
references

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Enable merge queue @goruha (#28) ## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners files

why

  • Support auto merge PRs
  • Create merge queue
  • Implement new CodeOwners policy
Enable merge queue @goruha (#27) ## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners files

why

  • Support auto merge PRs
  • Create merge queue
  • Implement new CodeOwners policy
chore(deps): bump golang.org/x/net from 0.34.0 to 0.38.0 in /test @[dependabot[bot]](https://github.com/apps/dependabot) (#18) Bumps [golang.org/x/net](https://github.com/golang/net) from 0.34.0 to 0.38.0.
Commits
  • e1fcd82 html: properly handle trailing solidus in unquoted attribute value in foreign...
  • ebed060 internal/http3: fix build of tests with GOEXPERIMENT=nosynctest
  • 1f1fa29 publicsuffix: regenerate table
  • 1215081 http2: improve error when server sends HTTP/1
  • 312450e html: ensure <search> tag closes <p> and update tests
  • 09731f9 http2: improve handling of lost PING in Server
  • 55989e2 http2/h2c: use ResponseController for hijacking connections
  • 2914f46 websocket: re-recommend gorilla/websocket
  • 99b3ae0 go.mod: update golang.org/x dependencies
  • 85d1d54 go.mod: update golang.org/x dependencies
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

chore(deps): update tflint plugin terraform-linters/tflint-ruleset-aws to v0.40.0 @[renovate[bot]](https://github.com/apps/renovate) (#19) This PR contains the following updates:
Package Type Update Change
terraform-linters/tflint-ruleset-aws plugin minor 0.38.0 -> 0.40.0

Release Notes

terraform-linters/tflint-ruleset-aws (terraform-linters/tflint-ruleset-aws)

v0.40.0

Compare Source

What's Changed

Enhancements
Chores

Full Changelog: terraform-linters/tflint-ruleset-aws@v0.39.0...v0.40.0

v0.39.0

Compare Source

What's Changed

Enhancements
Bug Fixes
Chores

New Contributors

Full Changelog: terraform-linters/tflint-ruleset-aws@v0.38.0...v0.39.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Enable merge queue @goruha (#26) ## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners files

why

  • Support auto merge PRs
  • Create merge queue
  • Implement new CodeOwners policy
Enable merge queue @goruha (#25) ## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners files

why

  • Support auto merge PRs
  • Create merge queue
  • Implement new CodeOwners policy
Enable merge queue @goruha (#24) ## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners files

why

  • Support auto merge PRs
  • Create merge queue
  • Implement new CodeOwners policy
Enable merge queue @goruha (#23) ## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners files

why

  • Support auto merge PRs
  • Create merge queue
  • Implement new CodeOwners policy
Enable merge queue @goruha (#22) ## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners files

why

  • Support auto merge PRs
  • Create merge queue
  • Implement new CodeOwners policy
Enable merge queue @goruha (#21) ## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners files

why

  • Support auto merge PRs
  • Create merge queue
  • Implement new CodeOwners policy
Enable merge queue @goruha (#20) ## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners files

why

  • Support auto merge PRs
  • Create merge queue
  • Implement new CodeOwners policy
chore(deps): bump golang.org/x/crypto from 0.32.0 to 0.35.0 in /test @[dependabot[bot]](https://github.com/apps/dependabot) (#17) Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.32.0 to 0.35.0.
Commits
  • 7292932 ssh: limit the size of the internal packet queue while waiting for KEX
  • f66f74b acme/autocert: check host policy before probing the cache
  • b0784b7 x509roots/fallback: drop obsolete build constraint
  • 911360c all: bump golang.org/x/crypto dependencies of asm generators
  • 89ff08d all: upgrade go directive to at least 1.23.0 [generated]
  • e47973b all: update certs for go1.24
  • 9290511 go.mod: update golang.org/x dependencies
  • fa5273e x509roots/fallback: update bundle
  • a8ea4be ssh: add ServerConfig.PreAuthConnCallback, ServerPreAuthConn (banner) interface
  • 71d3a4c acme: support challenges that require the ACME client to send a non-empty JSO...
  • See full diff in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Contributors

goruha
Assets 2
Loading