Skip to content

fix: add deployment boolean to job-environment-mapping schema (#6086)#6098

Closed
vanhci wants to merge 1 commit into
nektos:masterfrom
vanhci:fix/issue-6086-environment-deployment-schema
Closed

fix: add deployment boolean to job-environment-mapping schema (#6086)#6098
vanhci wants to merge 1 commit into
nektos:masterfrom
vanhci:fix/issue-6086-environment-deployment-schema

Conversation

@vanhci
Copy link
Copy Markdown

@vanhci vanhci commented May 21, 2026

Summary

Add the deployment boolean field to job-environment-mapping in the workflow schema to support the new GitHub Actions syntax that allows workflows to run in an environment without creating a deployment object.

Changes

  • Added deployment field (type: boolean) to job-environment-mapping.properties in pkg/schema/workflow_schema.json

Test Case

The following workflow now validates correctly:

jobs:
  example:
    runs-on: ubuntu-latest
    environment:
      name: production
      deployment: false  # New field
    steps:
      - run: echo "Hello"

Issue

Fixes #6086

Add the deployment field to job-environment-mapping to support the new
GitHub workflow syntax that allows workflows to run in an environment
without creating a deployment object.

Fixes: #6086
@vanhci vanhci closed this by deleting the head repository May 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

act --validate --strict fails with new environment: deployment: workflow setting.

1 participant