Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Puppet::ResourceApi::TypeDefinition#create_attribute_in when creating an invalid attribute errors cleanly Skipped: Not yet implemented

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Puppet::ResourceApi::TypeDefinition#create_attribute_in when creating an invalid attribute errors cleanly Skipped: Not yet implemented

exercising noop using `puppet resource` respects --noop Failure/Error: expect(stdout_str.strip).to match(/noop: true/) expected "\e[mNotice: /Test_noop_support[foo]/ensure: undefined 'ensure' from 'present' (noop)\e[0m\ntest_noop_support { 'foo': \n ensure => 'present',\n}" to match /noop: true/ Diff: @@ -1 +1,4 @@ -/noop: true/ +�[mNotice: /Test_noop_support[foo]/ensure: undefined 'ensure' from 'present' (noop) +test_noop_support { 'foo': + ensure => 'present', +}

exercising a type with device-specific providers using `puppet device` applies a catalog successfully Failure/Error: expect(stdout_str).to match(/Compiled catalog for some_node/) expected "\e[mNotice: Compiled catalog for other_node in environment production in 0.04 seconds\e[0m\n\e[0;32m.../cache/devices/other_node/state/state.yaml\e[0m\n\e[mNotice: Applied catalog in 0.01 seconds\e[0m\n" to match /Compiled catalog for some_node/ Diff: @@ -1 +1,9 @@ -/Compiled catalog for some_node/ +�[mNotice: Compiled catalog for other_node in environment production in 0.04 seconds +Info: Using environment 'production' +Info: Applying configuration version '1778718203' +�[mNotice: /Stage[main]/Main/Multi_device[foo]/ensure: defined 'ensure' as 'present' +�[mNotice: multi_device[foo]: Creating: Creating 'foo' with {:name=>"foo", :ensure=>"present"} +�[mNotice: multi_device[foo]: Creating: Finished in 0.000071 seconds +Info: Class[Main]: Unscheduling all events on Class[Main] +Info: Creating state file /home/runner/.puppetlabs/opt/puppet/cache/devices/other_node/state/state.yaml +�[mNotice: Applied catalog in 0.01 seconds

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

exercising a type with device-specific providers using `puppet device` applies a catalog successfully Failure/Error: expect(stdout_str).to match(/Compiled catalog for some_node/) expected "\e[mNotice: Compiled catalog for other_node in environment production in 0.11 seconds\e[0m\n\e[0;32m.../cache/devices/other_node/state/state.yaml\e[0m\n\e[mNotice: Applied catalog in 0.04 seconds\e[0m\n" to match /Compiled catalog for some_node/ Diff: @@ -1 +1,9 @@ -/Compiled catalog for some_node/ +�[mNotice: Compiled catalog for other_node in environment production in 0.11 seconds +Info: Using environment 'production' +Info: Applying configuration version '1778719199' +�[mNotice: /Stage[main]/Main/Multi_device[foo]/ensure: defined 'ensure' as 'present' +�[mNotice: multi_device[foo]: Creating: Creating 'foo' with {:name=>"foo", :ensure=>"present"} +�[mNotice: multi_device[foo]: Creating: Finished in 0.000333 seconds +Info: Class[Main]: Unscheduling all events on Class[Main] +Info: Creating state file C:/ProgramData/PuppetLabs/puppet/cache/devices/other_node/state/state.yaml +�[mNotice: Applied catalog in 0.04 seconds

Puppet::ResourceApi::TypeDefinition#create_attribute_in when creating an invalid attribute errors cleanly Skipped: Not yet implemented

exercising noop using `puppet resource` respects --noop Failure/Error: expect(stdout_str.strip).to match(/noop: true/) expected "\e[mNotice: /Test_noop_support[foo]/ensure: undefined 'ensure' from 'present' (noop)\e[0m\ntest_noop_support { 'foo': \n ensure => 'present',\n}" to match /noop: true/ Diff: @@ -1 +1,4 @@ -/noop: true/ +�[mNotice: /Test_noop_support[foo]/ensure: undefined 'ensure' from 'present' (noop) +test_noop_support { 'foo': + ensure => 'present', +}