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 #531

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 22, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
mkdocs-git-revision-date-localized-plugin == 1.2.9 -> ==1.3.0 age adoption passing confidence

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


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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Oct 22, 2024
Copy link

codacy-production bot commented Oct 22, 2024

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
+0.00% (target: -1.00%)
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (2128e86) 619 204 32.96%
Head commit (94eb39a) 619 (+0) 204 (+0) 32.96% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#531) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more

@github-actions github-actions bot added the Stale label Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file Stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants