Re: [I] bug: Apisix should reject configurations with missing plugin references [apisix]

2025-05-04 Thread via GitHub
Revolyssup commented on issue #12189: URL: https://github.com/apache/apisix/issues/12189#issuecomment-2850071785 @cruftex In the example you gave, I can see a configured plugin. What do you mean by "missing plugin references"? -- This is an automated message from the Apache Git Service. T

(apisix-dashboard) branch dependabot/github_actions/golangci/golangci-lint-action-8 created (now e4e7603f0)

2025-05-04 Thread github-bot
This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/github_actions/golangci/golangci-lint-action-8 in repository https://gitbox.apache.org/repos/asf/apisix-dashboard.git at e4e7603f0 chore(deps): bump golangci/golangci-lint-a

Re: [PR] chore(deps): bump golangci/golangci-lint-action from 3 to 7 [apisix-dashboard]

2025-05-04 Thread via GitHub
dependabot[bot] commented on PR #2992: URL: https://github.com/apache/apisix-dashboard/pull/2992#issuecomment-2850055523 Superseded by #3011. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the

(apisix-dashboard) branch dependabot/github_actions/golangci/golangci-lint-action-7 deleted (was 18e875937)

2025-05-04 Thread github-bot
This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/github_actions/golangci/golangci-lint-action-7 in repository https://gitbox.apache.org/repos/asf/apisix-dashboard.git was 18e875937 chore(deps): bump golangci/golangci-lint-a

Re: [PR] chore(deps): bump golangci/golangci-lint-action from 3 to 7 [apisix-dashboard]

2025-05-04 Thread via GitHub
dependabot[bot] closed pull request #2992: chore(deps): bump golangci/golangci-lint-action from 3 to 7 URL: https://github.com/apache/apisix-dashboard/pull/2992 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL abov

apisix-dashboard.git: Error while running github feature from dependabot/github_actions/golangci/golangci-lint-action-8:.asf.yaml

2025-05-04 Thread Apache Infrastructure
An error occurred while processing the github feature in .asf.yaml: while parsing a mapping in "apisix-dashboard.git/.asf.yaml::github", line 20, column 1: ^ (line: 20) unexpected key not in schema 'notifications' in "apisix-dashboard.git/.asf.yaml::github", line 24, column 1:

apisix-dashboard.git: Error while running github feature from --unknown-branch--:.asf.yaml

2025-05-04 Thread Apache Infrastructure
An error occurred while processing the github feature in .asf.yaml: while parsing a mapping in "apisix-dashboard.git/.asf.yaml::github", line 20, column 1: ^ (line: 20) unexpected key not in schema 'notifications' in "apisix-dashboard.git/.asf.yaml::github", line 24, column 1:

[PR] chore(deps): bump golangci/golangci-lint-action from 3 to 8 [apisix-dashboard]

2025-05-04 Thread via GitHub
dependabot[bot] opened a new pull request, #3011: URL: https://github.com/apache/apisix-dashboard/pull/3011 Bumps [golangci/golangci-lint-action](https://github.com/golangci/golangci-lint-action) from 3 to 8. Release notes Sourced from https://github.com/golangci/golangci-lint-act

[I] request help: Configuring APISIX Ingress Controller to Manage Multiple Independent Gateways (Control Planes) in Different Namespaces [apisix-ingress-controller]

2025-05-04 Thread via GitHub
Piyushgautamsingh opened a new issue, #2390: URL: https://github.com/apache/apisix-ingress-controller/issues/2390 ### Issue description **Question:** I'm setting up a decoupled APISIX deployment with the following architecture: - APISIX Ingress Controller in the `apisix-ingres

Re: [I] bug: nacos node failure should not corrupt in-memory data [apisix]

2025-05-04 Thread via GitHub
github-actions[bot] commented on issue #11252: URL: https://github.com/apache/apisix/issues/11252#issuecomment-2849122452 This issue has been marked as stale due to 350 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please si