renovate

History

Sergei Zharinov 8ea0538a0f refactor(maven): Change signatures for S3 resource checks (#31269 )		2024-09-09 05:22:03 +00:00
..
__fixtures__	fix(maven): Use correct snapshot URL in getDependencyInfo (#15380 )	2022-05-13 18:29:35 +02:00
__snapshots__	fix(maven): Return `isPrivate` flag for default repo (#31061 )	2024-08-28 05:22:16 +00:00
common.ts	refactor: lib/modules (#14488 )	2022-03-04 09:04:02 +01:00
index.spec.ts	fix(maven): Return `isPrivate` flag for default repo (#31061 )	2024-08-28 05:22:16 +00:00
index.ts	fix(maven): Return `isPrivate` flag for default repo (#31061 )	2024-08-28 05:22:16 +00:00
readme.md	chore(docs/maven): document how to specify project homepage in pom.xml (#22889 )	2023-06-20 09:40:21 +00:00
s3.spec.ts	fix(maven): Return `isPrivate` flag for default repo (#31061 )	2024-08-28 05:22:16 +00:00
types.ts	refactor(maven): Use explicit cacheability flag for datasource (#15110 )	2022-04-14 09:37:07 +02:00
util.spec.ts	refactor(maven): Change signatures for S3 resource checks (#31269 )	2024-09-09 05:22:03 +00:00
util.ts	refactor(maven): Change signatures for S3 resource checks (#31269 )	2024-09-09 05:22:03 +00:00

readme.md

Making your changelogs fetchable

In case you are publishing artifacts and you want to ensure that your changelogs are fetchable by Renovate, you need to configure the scm section on their pom.xml file.

For example:

<scm>
    <url>scm:git:https://github.com/path_to_repository</url>
</scm>

This is what allows Renovate to determine the sourceUrl, that it then uses to fetch the changelogs.

!!! note This also works for private repositories. It can leverage the same token that you had to configure in order to be able to reach the private Artifactory.

Specifying your project homepage

When opening a Pull Request Renovate uses the top level url property to determine the homepage of your project and shows it inside the Pull Request. To customize you can set it inside your pom.xml.

For example:

<url>https://project.example.com</url>