chore: deprecate ci environment

[hiento09]

This pull request removes the environment: production setting from several GitHub Actions workflows. These changes simplify the configuration and align the workflows with updated practices.

Workflow configuration updates:

• .github/workflows/publish-npm-core.yml: Removed environment: production from the build-and-publish-plugins job configuration.
• .github/workflows/template-electron-build-linux-x64.yml: Removed environment: production from the build-linux-x64 job configuration.
• .github/workflows/template-electron-build-macos.yml: Removed environment: production from the build-macos job configuration.
• .github/workflows/template-get-update-version.yml: Removed environment: production from the get-update-version job configuration.
• .github/workflows/template-noti-discord-and-update-url-readme.yml: Removed environment: production from the noti-discord-and-update-url-readme job configuration.

---

Important

Remove environment: production from multiple GitHub Actions workflows to simplify configuration.

• Workflow Configuration Updates:
  • Removed environment: production from build-and-publish-plugins in publish-npm-core.yml.
  • Removed environment: production from build-linux-x64 in template-electron-build-linux-x64.yml.
  • Removed environment: production from build-macos in template-electron-build-macos.yml.
  • Removed environment: production from get-update-version in template-get-update-version.yml.
  • Removed environment: production from noti-discord-and-update-url-readme in template-noti-discord-and-update-url-readme.yml.

^{This description was created by for a4e8a34. You can customize this summary. It will automatically update as commits are pushed.}

[hiento09]

Related issue #5453

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to a4e8a34 in 1 minute and 12 seconds. Click for details.

• Reviewed 133 lines of code in 7 files
• Skipped 0 files when reviewing.
• Skipped posting 7 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. .github/workflows/publish-npm-core.yml:9

• Draft comment:
  Removed 'environment: production' from the 'build-and-publish-plugins' job. Ensure that any required production approval or gating is handled elsewhere.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the author to ensure that production approval or gating is handled elsewhere, which violates the rule against asking the author to ensure behavior is intended or tested. It doesn't provide a specific code suggestion or ask for a specific test to be written.

2. .github/workflows/template-electron-build-linux-x64.yml:44

• Draft comment:
  Removed 'environment: production' from the 'build-linux-x64' job to simplify the workflow configuration. This change is consistent with updated practices.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, explaining a change that was made without asking for any specific action or providing a suggestion. It doesn't align with the rules for useful comments.

3. .github/workflows/template-electron-build-macos.yml:54

• Draft comment:
  Removed 'environment: production' from the 'build-macos' job. The change aligns with updated workflow standards.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, explaining a change that was made without providing any actionable feedback or suggestions. It doesn't ask for confirmation or suggest any improvements.

4. .github/workflows/template-get-update-version.yml:10

• Draft comment:
  Removed 'environment: production' from the 'get-update-version' job. Verify that any intended access controls are maintained elsewhere.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the author to verify that access controls are maintained elsewhere after a change. This falls under asking the author to ensure behavior is intended, which is against the rules.

5. .github/workflows/template-noti-discord-and-update-url-readme.yml:28

• Draft comment:
  Removed 'environment: production' from the 'noti-discord-and-update-url-readme' job to streamline the workflow configuration.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, explaining a change made in the code without providing any actionable feedback or suggestions. It does not align with the rules for useful comments.

6. .github/workflows/template-tauri-build-linux-x64.yml:56

• Draft comment:
  Removed 'environment: production' from the tauri Linux build job. This removal simplifies the configuration and is consistent with other workflows.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, explaining a change made in the PR without suggesting any action or asking for clarification. It doesn't align with the rules for useful comments.

7. .github/workflows/template-tauri-build-macos.yml:64

• Draft comment:
  Removed 'environment: production' from the tauri macOS build job. Confirm that any environment-specific approvals or controls are addressed as needed.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to confirm that environment-specific approvals or controls are addressed, which violates the rule against asking for confirmation or ensuring behavior is intended. It does not provide a specific code suggestion or ask for a specific test to be written.

Workflow ID: wflow_JZwNL7TDLQCE9rzp

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}