deps-dev(deps-dev): bump @semantic-release/release-notes-generator from 12.1.0 to 14.1.0#7
Open
dependabot[bot] wants to merge 45 commits into
Conversation
Author
AssigneesThe following users could not be added as assignees: LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
…mentation - Simplified and clarified project description and features - Added comprehensive Shelly GitHub integration documentation - Included gap analysis and improvement roadmap - Enhanced troubleshooting section with Shelly-specific solutions - Improved architecture diagram and command reference - Streamlined installation and configuration instructions
- Updated all OpenAI references to Vertex AI throughout README - Changed configuration examples to use Google Cloud credentials - Updated environment variables for Vertex AI setup - Fixed architecture diagram to show Vertex AI PaLM - Corrected troubleshooting commands for Google Cloud - Updated planned improvements to mention PaLM 2 and Gemini Pro
- Create detailed commit policy document for Juspay organization standards - Define conventional commit message format with NeuroPulse-specific scopes - Include workflow guidelines for contributors and maintainers - Add integration guidelines for Jira, AI, and Slack workflows - Specify emergency procedures and exception handling - Include tools and automation for policy enforcement - Add training resources and onboarding checklist Establishes professional git standards for enterprise-level development
…roubleshooting - Update repository URL to juspay/NeuroPulse organization - Replace misleading 'solved gaps' with honest current status tracking - Document actual GitHub authentication errors encountered - Add comprehensive troubleshooting for enterprise security policies - Include step-by-step solutions for fine-grained token setup - Add emergency procedures and rollback instructions - Provide detailed Vertex AI configuration troubleshooting - Include real error messages and specific command-line solutions Ensures documentation reflects reality and helps users solve actual problems
- Move comprehensive troubleshooting from README to docs/TROUBLESHOOTING.md - Keep concise troubleshooting section in README with quick fixes - Add clear links to detailed troubleshooting guide - Enhance TROUBLESHOOTING.md with enterprise-specific solutions - Include step-by-step guides for all major issues encountered - Add emergency procedures and performance optimization guides - Improve documentation organization and accessibility Makes README more focused while providing comprehensive help in dedicated file
- Add working .mcp-config.json configuration (resolves 'Found 0 MCP servers') - Add .mcp-config.json.example template for user setup - Create comprehensive docs/MCP_SETUP.md setup guide - Add SLACK_JIRA_INTEGRATION.md with step-by-step connection instructions - Document Shelly GitHub authentication issues in SHELLY_GITHUB_ISSUE.md - Update README.md with MCP Server Integration section - Enhance docs/TROUBLESHOOTING.md with MCP error resolution This resolves the critical 'Found 0 MCP servers' error that was blocking AI tool integration with NeuroLink. The filesystem server now connects successfully with 14 available tools. Fixes: #11 Related: Enterprise GitHub authentication challenges
- Update NeuroLink to v7.53.5 to resolve MCP protocol compatibility - Add detailed MCP troubleshooting guide to docs/MCP_SETUP.md - Fix MCP error -32601 'Method not found' issue - Add working configuration for Slack, Jira, and filesystem MCP servers - Include SLACK_TEAM_ID requirement for Slack MCP server - Document version compatibility matrix and solutions
- Resolve conflicts in README.md and docs/PROJECT_STRUCTURE.md - Integrate remote changes with local MCP documentation updates - Maintain comprehensive documentation structure from both branches
- Remove .mcp-config.json from repository to prevent accidental token exposure - Add .mcp-config.json to .gitignore for future protection - Users should copy .mcp-config.json.example to .mcp-config.json locally - Resolves GitHub push protection violations for secret scanning
Bumps [@semantic-release/release-notes-generator](https://github.com/semantic-release/release-notes-generator) from 12.1.0 to 14.1.0. - [Release notes](https://github.com/semantic-release/release-notes-generator/releases) - [Commits](semantic-release/release-notes-generator@v12.1.0...v14.1.0) --- updated-dependencies: - dependency-name: "@semantic-release/release-notes-generator" dependency-version: 14.1.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/semantic-release/release-notes-generator-14.1.0
branch
from
016ebd7 to
062e552
Compare
Swetha-160303
force-pushed
the
release
branch
from
78fc5dc to
9e35a8d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps @semantic-release/release-notes-generator from 12.1.0 to 14.1.0.
Release notes
Sourced from
@semantic-release/release-notes-generator's releases.... (truncated)
Commits
485bc0afeat(preset): support ignoreCommits option (#836)fc8464bdocs(conventionalcommits): update link to options for the conventionalcommits...45d87a1chore(deps): lock file maintenance (#837)236f298chore(deps): lock file maintenance (#835)7f5bb7fci(action): update actions/checkout action to v5 (#834)c31c651ci(action): update actions/checkout action to v4.3.0 (#833)5453abachore(deps): lock file maintenance (#832)a2e1560chore(deps): update dependency fs-extra to v11.3.1 (#831)b65a3fdchore(deps): lock file maintenance (#830)f40710bchore(deps): update npm to v11 (#828)You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)