cloudfoundry / cloudfoundry/java-buildpack-release

java-buildpack-release v4.77.0 contains v4.76.0 packages

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
1
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Hello everyone,

One of the latest cf-deployment releases, which contains in its manifest java-buildpack-release v4.77.0, after deploying it, still shows java-buildpack v4.76.0 with java-buildpack-cflinuxfs3-v4.76.0.zip and java-buildpack-cflinuxfs4-v4.76.0.zip files respectively.

Inspection of v4.77.0 bosh release shows that it contains v4.76.0 packages inside.

I would guess that it happened because of recent changes in releasing pipeline.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the java-buildpack-release v4.77.0 BOSH release with the v4.76.0 packages referenced in the issue, and then inspect the recent release-pipeline changes mentioned. Done means v4.77.0 contains matching java-buildpack v4.77.0 package files for both cflinuxfs3 and cflinuxfs4.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.