dev: bump go.thethings.network/lorawan-stack/v3 from 3.28.2 to 3.29.0

[dependabot[bot]]

Bumps go.thethings.network/lorawan-stack/v3 from 3.28.2 to 3.29.0.

Release notes

Sourced from go.thethings.network/lorawan-stack/v3's releases.

v3.29.0

Added

• relays command to ttn-lw-cli, which enables the management of LoRaWAN relays, including their configuration and uplink forwarding rules.

Changed

• User's primary email address validation is now decoupled from deprecated ContactInfo field.
  • This requires a database schema migration (ttn-lw-stack is-db migrate) because of the new email_validations table.
• Entities' ContactInfo field now returns information regarding the administrative and technical contacts instead of the deprecated ContactInfo information.
  • This requires a database schema migration (ttn-lw-stack is-db migrate) due to the removal of old information in the contact_infos table.
  • The emails of the administrative and technical contacts are only returned in the ContactInfo field if the caller has the appropriate rights.
• Organizations can now opt out from sending administrative and technical notifications to all collaborators.
  • New organizations do not send administrative and technical notifications to all collaborators by default.
  • To alter the behavior update the organization's fanout_notifications field.

Removed

• The http.client.transport.compression and http.server.transport.compression experimental flags.

Fixed

• Fix Add collaborator form not validating collaborator on submit in the Console.

Changelog

Sourced from go.thethings.network/lorawan-stack/v3's changelog.

[3.29.0] - 2024-02-06

Added

• relays command to ttn-lw-cli, which enables the management of LoRaWAN relays, including their configuration and uplink forwarding rules.

Changed

• User's primary email address validation is now decoupled from deprecated ContactInfo field.
  • This requires a database schema migration (ttn-lw-stack is-db migrate) because of the new email_validations table.
• Entities' ContactInfo field now returns information regarding the administrative and technical contacts instead of the deprecated ContactInfo information.
  • This requires a database schema migration (ttn-lw-stack is-db migrate) due to the removal of old information in the contact_infos table.
  • The emails of the administrative and technical contacts are only returned in the ContactInfo field if the caller has the appropriate rights.
• Organizations can now opt out from sending administrative and technical notifications to all collaborators.
  • New organizations do not send administrative and technical notifications to all collaborators by default.
  • To alter the behavior update the organization's fanout_notifications field.

Removed

• The http.client.transport.compression and http.server.transport.compression experimental flags.

Fixed

• Fix Add collaborator form not validating collaborator on submit in the Console.

Commits

• 7d1e643 all: Enter release date of version 3.29.0 into the changelog
• 5660ea1 dev: Update build space settings
• 1690c70 dev: Update changelog
• 470de96 all: Bump to version 3.29.0
• b22ff70 Merge pull request #6910 from TheThingsNetwork/changelog/v3.29.0
• 0d4ad94 all: Cut off changelog version 3.29.0
• 69608ea Merge pull request #6906 from TheThingsNetwork/feature/group-dependabot
• 9b987b5 dev: Group dependabot PRs
• 9b518bd Merge pull request #6891 from TheThingsNetwork/dependabot/go_modules/github.c...
• 79ee72f Merge pull request #6894 from TheThingsNetwork/dependabot/github_actions/gola...
• Additional commits viewable in compare view

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 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)