Apparently regular PR come with `Secrets source: none` (for `on: pull_request` GHA event).
So, no any secrets are available to be propagated down to the repository configurations.
And that is indeed a good sign to not let any unexpected PR to be built.
On the other hand, the Dependabot updates are OK and its PRs come with `Secrets source: dependabot`.
So, we are good to auth repositories to build those PRs and merge.
* Mention secrets limitation in the `pr-build.yml`
* Fix `commercial-settings.gradle` to check if Dependabot is running our project build.
Change repositories respectively, and set provided credentials
* Upgrade to Gradle `8.4` and latest plugins for Develocity (formerly Gradle Enterprise)
* Add GHA workflows based on a common repository with reusable workflows
* Remove `release-files-spec.json` as it is supplied by common repo on respective CI/CD phase
* Remove obsolete GHA workflows
* Fix deprecation in the `AbstractTestContainerTests`
* Change developer roles and emails
Initial Commit for Spring Framework 6.0/JDK 17
* Fix add-opens for java.util.zip; add distributionSha256Sum to gradle.properties.
Fix remaining errors of migration to SF-6.0
* Remove `lineSeparator` property for `NewlineAtEndOfFile` Checkstyle rule:
Windows checkouts files with a `crlf` line feed
* Add `-Dfile.encoding=UTF-8` jmvarg for Gradle: some source files use non-UTF symbols
* Upgrade to Kotlin `1.5.31`, JSON Path `2.6.0`, Junit `5.8.1`
* Use correct links for external JavaDocs
* Add `Xdoclint:syntax` to JavaDoc Gradle task to suppress JavaDoc warnings for classes
* Use `DuplicatesStrategy.EXCLUDE` for `prepareAsciidocBuild` task
* Align `api` task with SF style
Add `Xdoclint:syntax` to `api` Gradle task
Turns out `api` task generates fresh common JavaDocs,
so it emits the same warnings for missed docs in classes
Remove files restored by rebase
Fix test Java version
Fix build.gradle
Resolves https://github.com/spring-projects/spring-amqp/issues/1309
If the `RabbitTemplate` was called from a `@TransactionalEventListener`,
with phase `AFTER_COMMIT`, a transaction is "active", but synchronizations
are already cleared. It is too late to synchronize this transaction.
We end up with an orphaned `ResourceHolder` with pending transaction commits.
Don't bind the resource holder if synchronization is not active.
However, the proper solution, if users want to synchronize the rabbit transaction
with the global transaction, is to use the `BEFORE_COMMIT` phase.
See the discussion on the Github issue for more information.
**cherry-pick to 2.2.x**
* Fix since version.
* Reset physical close required flag left over from another test.
* Capture test results for all modules.
* Remove `.travis.yml` since we rely now on GH Actions for PR checks
* Remove all the Travis mentioning when we couldn't pass build because of memory
* Fix `Arnaud Cogoluègnes` name in the `@author` list
