Skip to content

Replace deprecated set-output usage with GITHUB_OUTPUT environment files #42

Description

@gingeekrishna

Summary\n�ws-issue-triage-manager still uses deprecated output handling, which causes downstream GitHub Actions jobs to fail/warn in repositories that consume this action.\n\n## Current behavior\nThe action code initializes outputs using core.setOutput(...) (compiled dist/index.js and source path equivalent).\nThis maps to the deprecated ::set-output command behavior.\n\n## Why this matters\nGitHub Actions deprecated set-output in favor of environment files. Consumers are now seeing failures or policy blocks in automation pipelines.\n\nReferences:\n- https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/\n- https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter\n\n## Requested fix\nUse environment files ($GITHUB_OUTPUT) for action outputs instead of set-output.\n\nFor JavaScript/TypeScript actions, equivalent pattern:\n`js\nconst fs = require('fs');\nfs.appendFileSync(process.env.GITHUB_OUTPUT,

ame=\n);\n`\n\nAdditionally, consider updating action runtime in �ction.yml to a currently supported Node runtime if needed.\n\n## Consumer impact example\nIn �ws/aws-cdk PR automation, workflow issue-label-assign.yml consumes this action and receives deprecated output related failures/warnings unrelated to feature code under test.\n

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions