Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency mkdocs-git-revision-date-localized-plugin to v1.3.0 #7

Conversation

homarr-renovate[bot]
Copy link
Contributor

This PR contains the following updates:

Package Update Change
mkdocs-git-revision-date-localized-plugin minor ==1.2.5 -> ==1.3.0

Release Notes

timvink/mkdocs-git-revision-date-localized-plugin (mkdocs-git-revision-date-localized-plugin)

v1.3.0: revision-date-localized v1.3.0

Compare Source

What's Changed

🟠 Minor breaking changes: This release will change some of the git revision dates:

  • We now ignore changes to files that only contain whitespaces or blanklines, as these are not 'real' revisions to the content. This maps to the git log --ignore_all_space --ignore_blank_lines.
  • We now ignore rename commits for determining the last revision date, as these are not 'real' revisions to the content. This maps to the git log diff-filter=r command (see git log docs)
  • We will now follow changes to a file across file renames (including moving files around). This maps to git log --follow. While giving more accurate revision and creation dates, there is an edge case: if you commit empty files, the revision date might wrong. For details see this blogpost. You can opt-out of this behavior by using the new option enable_git_follow (which defaults to True). If you still hit inaccurate revision dates for specific files, consider manually defining them.

Pull requests:

New Contributors

Full Changelog: timvink/mkdocs-git-revision-date-localized-plugin@v1.2.9...v1.3.0

v1.2.9: revision-date-localized v1.2.9

Compare Source

What's Changed

New Contributors

Full Changelog: timvink/mkdocs-git-revision-date-localized-plugin@v1.2.8...v1.2.9

v1.2.8: revision-date-localized v1.2.8

Compare Source

What's Changed

New Contributors

Full Changelog: timvink/mkdocs-git-revision-date-localized-plugin@v1.2.6...v1.2.8

v1.2.7: revision-date-localized v1.2.7

Compare Source

What's Changed

New Contributors

Full Changelog: timvink/mkdocs-git-revision-date-localized-plugin@v1.2.6...v1.2.7

v1.2.6: revision-date-localized v1.2.6

Compare Source

What's Changed

Full Changelog: timvink/mkdocs-git-revision-date-localized-plugin@v1.2.5...v1.2.6


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 has been generated by Renovate Bot.

@homarr-renovate
Copy link
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@oben01 oben01 closed this Jan 18, 2025
@oben01 oben01 deleted the renovate/mkdocs-git-revision-date-localized-plugin-1.x branch January 18, 2025 19:08
@homarr-renovate
Copy link
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (==1.3.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant