microsoft / microsoft/kiota-java

Investigate GitHub release workflow failure despite updating assets as expected

Open
#1,612 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
38
Forks
34
Avg merge
15h 9m
Merged PRs (30d)
20

Description

GitHub release is updated with expected assets but job ends in an [error state](https://github.com/microsoft/kiota-java/actions/runs/11240262608/job/31249201999#logs)

Context:
Kiota Java now uses release please which is working as expected for the latest release: [release PR](https://github.com/microsoft/kiota-java/pull/1611), [tag & GH release with assets](https://github.com/microsoft/kiota-java/releases/tag/v1.6.0)

Investigate error state when updating the release with assets

Contributor guide

Open the contributing guide

Research direction

Start with the linked GitHub Actions job logs and compare the failing run with release PR #1611 and the v1.6.0 tag and GitHub release. Identify why the job reports an error despite publishing the expected assets, then verify that a subsequent release workflow completes successfully without changing the assets.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, github-actions
Domain
ci-cd, 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.