search

borgmatic-collective / docker-borgmatic

Borgmatic in Docker
GNU General Public License v3.0
314 stars 88 forks source link

Bump borgmatic from 1.7.15 to 1.8.0 #247

Closed dependabot[bot] closed 11 months ago

dependabot[bot] commented 11 months ago

Bumps borgmatic from 1.7.15 to 1.8.0.

Release notes

Sourced from borgmatic's releases.

borgmatic 1.8.0

  • #575: BREAKING: For the "borgmatic borg" action, instead of implicitly injecting repository/archive into the resulting Borg command-line, pass repository to Borg via an environment variable and make archive available for explicit use in your commands. See the documentation for more information: https://torsion.org/borgmatic/docs/how-to/run-arbitrary-borg-commands/
  • #719: Fix an error when running "borg key export" through borgmatic.
  • #720: Fix an error when dumping a database and the "exclude_nodump" option is set.
  • #724: Add "check_i_know_what_i_am_doing" option to bypass Borg confirmation prompt when running "check --repair".
  • When merging two configuration files, error gracefully if the two files do not adhere to the same format.
  • #721: Remove configuration sections ("location:", "storage:", "hooks:" etc.), while still keeping deprecated support for them. Now, all options are at the same level, and you don't need to worry about commenting/uncommenting section headers when you change an option (if you remove your sections first).
  • #721: BREAKING: The retention prefix and the consistency prefix can no longer have different values (unless one is not set).
  • #721: BREAKING: The storage umask and the hooks umask can no longer have different values (unless one is not set).
  • BREAKING: Flags like "--config" that previously took multiple values now need to be given once per value, e.g. "--config first.yaml --config second.yaml" instead of "--config first.yaml second.yaml". This prevents argument parsing errors on ambiguous commands.
  • BREAKING: Remove the deprecated (and silently ignored) "--successful" flag on the "list" action, as newer versions of Borg list successful (non-checkpoint) archives by default.
  • All deprecated configuration option values now generate warning logs.
  • Remove the deprecated (and non-functional) "--excludes" flag in favor of excludes within configuration.
  • Fix an error when logging too-long command output during error handling. Now, long command output is truncated before logging.
Changelog

Sourced from borgmatic's changelog.

1.8.0

  • #575: BREAKING: For the "borgmatic borg" action, instead of implicitly injecting repository/archive into the resulting Borg command-line, pass repository to Borg via an environment variable and make archive available for explicit use in your commands. See the documentation for more information: https://torsion.org/borgmatic/docs/how-to/run-arbitrary-borg-commands/
  • #719: Fix an error when running "borg key export" through borgmatic.
  • #720: Fix an error when dumping a database and the "exclude_nodump" option is set.
  • #724: Add "check_i_know_what_i_am_doing" option to bypass Borg confirmation prompt when running "check --repair".
  • When merging two configuration files, error gracefully if the two files do not adhere to the same format.
  • #721: Remove configuration sections ("location:", "storage:", "hooks:" etc.), while still keeping deprecated support for them. Now, all options are at the same level, and you don't need to worry about commenting/uncommenting section headers when you change an option (if you remove your sections first).
  • #721: BREAKING: The retention prefix and the consistency prefix can no longer have different values (unless one is not set).
  • #721: BREAKING: The storage umask and the hooks umask can no longer have different values (unless one is not set).
  • BREAKING: Flags like "--config" that previously took multiple values now need to be given once per value, e.g. "--config first.yaml --config second.yaml" instead of "--config first.yaml second.yaml". This prevents argument parsing errors on ambiguous commands.
  • BREAKING: Remove the deprecated (and silently ignored) "--successful" flag on the "list" action, as newer versions of Borg list successful (non-checkpoint) archives by default.
  • All deprecated configuration option values now generate warning logs.
  • Remove the deprecated (and non-functional) "--excludes" flag in favor of excludes within configuration.
  • Fix an error when logging too-long command output during error handling. Now, long command output is truncated before logging.
Commits
  • 0ad7b4f Bump version for release.
  • 5c94160 Clarify database version description.
  • 5e0283b Remove broken markdown item.
  • ac0b239 Satisfy Gitea validation.
  • cde50a7 Attempt to add some vertical whitespace for clarity.
  • 521c0eb Fix text areas in issue templates.
  • bc5dc22 Convert issue templates from Markdown to YAML to take advantage of forms.
  • 973ab01 Disable submitting issues without a template.
  • 9413a19 Try out multiple Gitea templates.
  • 0055de0 Merge branch 'main' of ssh://projects.torsion.org:3022/borgmatic-collective/b...
  • Additional commits viewable 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 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)
dependabot[bot] commented 11 months ago

Superseded by #249.