[Bug][Github][Release] Releases data not collected (cicd_releases empty)

[caioq]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

I am encountering an issue where GitHub release data is not being collected into the cicd_releases table. I'm running DevLake v20250513@a4406df and executing a pipeline that includes the "Extract Releases" and "Convert Releases" subtasks. Although the pipeline completes successfully, no records are inserted into cicd_releases.

Upon investigating the database, I found that the _raw_github_graphql_release table, which I expected to contain raw release data, does not exist. I then located a migration script in the DevLake codebase (https://github.com/apache/incubator-devlake/blob/main/backend/plugins/github_graphql/model/migrationscripts/20240808_flush_rawdata.go#L40) that explicitly drops this table.

This leads me to believe that the method for collecting GitHub release data may have changed or been deprecated. The current pipeline, despite appearing to succeed, is not populating the necessary cicd_releases table.

Pipeline Logs:

time="2025-06-26 12:49:42" level=info msg=" [pipeline service] [pipeline #354] [task #31002] executing subtask Extract Releases"
time="2025-06-26 12:49:42" level=info msg=" [pipeline service] [pipeline #354] [task #31002] subtask Extract Releases finished in 11 ms"
time="2025-06-26 12:49:42" level=info msg=" [pipeline service] [pipeline #354] [task #31002] finished step: 1 / 2"
time="2025-06-26 12:49:42" level=info msg=" [pipeline service] [pipeline #354] [task #31002] executing subtask Convert Releases"
time="2025-06-26 12:49:42" level=info msg=" [pipeline service] [pipeline #354] [task #31002] subtask Convert Releases finished in 5 ms"
time="2025-06-26 12:49:42" level=info msg=" [pipeline service] [pipeline #354] [task #31002] finished step: 2 / 2"

What do you expect to happen

I expect the pipeline to successfully collect GitHub release data and populate the cicd_releases table. If the _raw_github_graphql_release table is indeed deprecated, I need to understand the new, recommended approach for collecting GitHub release data using DevLake.

How to reproduce

1. Set up Apache DevLake with a GitHub connection.
2. Create a blueprint that includes the "GitHub" plugin.
3. Ensure the "Extract Releases" and "Convert Releases" subtasks are enabled in your pipeline for a GitHub repository that has existing releases.
4. Run the pipeline.
5. After the pipeline completes, check the cicd_releases table in the DevLake database. Observe that it is empty.
6. Verify that the _raw_github_graphql_release table does not exist in the database.

Anything else

Given the migration script dropping _raw_github_graphql_release, I suspect the GitHub releases feature, as implemented via GraphQL, might have been moved to a different collection mechanism.

Version

v20250513@a4406df

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[dosubot]

The GitHub releases collection feature in DevLake has been fundamentally changed. The old raw table, _raw_github_graphql_release, was intentionally dropped as part of a migration to a new storage approach, but there is currently no direct replacement or new extraction logic for GitHub releases in the latest codebase. The "Extract Releases" and "Convert Releases" subtasks are still registered, but they act as no-ops—they finish immediately without collecting or converting any data, which matches your pipeline logs. This means GitHub release data is not being collected or populated into cicd_releases at this time, and there is no alternative or recommended method available in v20250513@a4406df. For now, monitoring future release notes or discussions is the best way to track if/when this feature is restored or replaced.
Reference: migration script dropping the table

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[github-actions]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.