SongodaCore/.github/dependabot.yml

version: 2
updates:
  - package-ecosystem: maven
    directory: /
    target-branch: development
    schedule:
      interval: monthly

  - package-ecosystem: github-actions
    directory: /
    target-branch: development
    schedule:
      interval: monthly
Introduce new CI/CD pipeline using GitHub Actions A lot is happening in this release! tl;dr: GitHub Actions runs tests, compiles the project, signs the jar files, deploys them to the Maven repo; Pushing a git tag issues a release instead of snapshot deployment; -SNAPSHOT is always added to the version otherwise; Core Version is now injected by maven instead of manually updating it in one of the classes We now use GitHub Actions to run automated tests, compile the project, sign the resulting jar files, and always deploy a version to the Maven repo. By default, a snapshot release is published but by creating a git tag, a release deploy can be triggered. Additionally the Core version is not manually updated in one of the classes but injected after compiling it. I think I found the most stable and easiest way to do this in maven, although I'd have wished for it to be easier and maybe not after the class file has already been created. 2022-08-07 19:33:38 +02:00			`version: 2`
			`updates:`
Cleanup YAML in `.github/dependabot.yml` 2022-11-25 23:59:44 +01:00			`- package-ecosystem: maven`
			`directory: /`
			`target-branch: development`
Introduce new CI/CD pipeline using GitHub Actions A lot is happening in this release! tl;dr: GitHub Actions runs tests, compiles the project, signs the jar files, deploys them to the Maven repo; Pushing a git tag issues a release instead of snapshot deployment; -SNAPSHOT is always added to the version otherwise; Core Version is now injected by maven instead of manually updating it in one of the classes We now use GitHub Actions to run automated tests, compile the project, sign the resulting jar files, and always deploy a version to the Maven repo. By default, a snapshot release is published but by creating a git tag, a release deploy can be triggered. Additionally the Core version is not manually updated in one of the classes but injected after compiling it. I think I found the most stable and easiest way to do this in maven, although I'd have wished for it to be easier and maybe not after the class file has already been created. 2022-08-07 19:33:38 +02:00			`schedule:`
Cleanup YAML in `.github/dependabot.yml` 2022-11-25 23:59:44 +01:00			`interval: monthly`
Introduce new CI/CD pipeline using GitHub Actions A lot is happening in this release! tl;dr: GitHub Actions runs tests, compiles the project, signs the jar files, deploys them to the Maven repo; Pushing a git tag issues a release instead of snapshot deployment; -SNAPSHOT is always added to the version otherwise; Core Version is now injected by maven instead of manually updating it in one of the classes We now use GitHub Actions to run automated tests, compile the project, sign the resulting jar files, and always deploy a version to the Maven repo. By default, a snapshot release is published but by creating a git tag, a release deploy can be triggered. Additionally the Core version is not manually updated in one of the classes but injected after compiling it. I think I found the most stable and easiest way to do this in maven, although I'd have wished for it to be easier and maybe not after the class file has already been created. 2022-08-07 19:33:38 +02:00
Cleanup YAML in `.github/dependabot.yml` 2022-11-25 23:59:44 +01:00			`- package-ecosystem: github-actions`
			`directory: /`
			`target-branch: development`
Introduce new CI/CD pipeline using GitHub Actions A lot is happening in this release! tl;dr: GitHub Actions runs tests, compiles the project, signs the jar files, deploys them to the Maven repo; Pushing a git tag issues a release instead of snapshot deployment; -SNAPSHOT is always added to the version otherwise; Core Version is now injected by maven instead of manually updating it in one of the classes We now use GitHub Actions to run automated tests, compile the project, sign the resulting jar files, and always deploy a version to the Maven repo. By default, a snapshot release is published but by creating a git tag, a release deploy can be triggered. Additionally the Core version is not manually updated in one of the classes but injected after compiling it. I think I found the most stable and easiest way to do this in maven, although I'd have wished for it to be easier and maybe not after the class file has already been created. 2022-08-07 19:33:38 +02:00			`schedule:`
Cleanup YAML in `.github/dependabot.yml` 2022-11-25 23:59:44 +01:00			`interval: monthly`