Repository navigation
[maven-release-plugin] prepare for next development iteration #661
cowtowncoderAnnotations
9 warnings
|
build (17)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332, actions/setup-java@6a0805fcefea3d4657a47ac4c165951e33482018. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build (17)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0sGmwagAAAABfj9qY3IOKSZOjULcw9tuEUEhYMzFFREdFMDIwOQBFZGdl
|
|
build (17)
Failed to restore: Cache service responded with 400
|
|
build (21)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332, actions/setup-java@6a0805fcefea3d4657a47ac4c165951e33482018. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build (21)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0t2mwagAAAAAFZsgkKMPUQYFcUgD5wEMuQ0gxQUEyMDMwODEzMDI1AEVkZ2U=
|
|
build (21)
Failed to restore: Cache service responded with 400
|
|
build (8)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332, actions/setup-java@6a0805fcefea3d4657a47ac4c165951e33482018. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build (8)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0wGmwagAAAAAzb5Q2UynoSq6LZT28NGHzU0xDMzFFREdFMDExMABFZGdl
|
|
build (8)
Failed to restore: Cache service responded with 400
|