Skip to content

Merge release/2.0.3 into master#317

Merged
vypbot merged 21 commits intomasterfrom
release/2.0.3
Feb 17, 2026
Merged

Merge release/2.0.3 into master#317
vypbot merged 21 commits intomasterfrom
release/2.0.3

Conversation

@vypbot
Copy link
Contributor

@vypbot vypbot commented Feb 17, 2026

🚀 Automated Merge

This PR merges release/2.0.3 into master.

Commits included:

Merge release/2.0.2 into develop

  • bugfix-314-error-merging-release-branch-after-successful-deployment: Enhance documentation and implementation for deploy label and merge flow. Added new sections in README and index.mdx, and improved MergeRepository to wait for PR-specific check runs before merging. Updated tests for MergeRepository and DeployedActionUseCase to cover new behavior and ensure correctness in handling merges and check waits.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Enhance MergeRepository and DeployedActionUseCase documentation to clarify PR-specific check run handling and deployment flow. Updated comments and type definitions to reflect new behavior, ensuring better understanding of the merging process and check wait logic.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Enhance MergeRepository to handle fallback to status checks when no PR-specific check runs are available after polling. Added test case to verify that the merge process correctly waits for pending status checks before proceeding. This improves the robustness of the merging logic and ensures proper handling of check statuses.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Enhance logging functionality by introducing accumulated log management. Added methods to clear and retrieve accumulated logs, and updated log functions to support accumulation. Implemented tests to verify the correct behavior of log accumulation and formatting, ensuring robust logging capabilities.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Enhance IssueRepository and publishFindings functionality to support commit SHA watermarks in comments. Updated addComment and updateComment methods to accept an options parameter for commitSha, allowing comments to include a link to the specific commit. Adjusted related tests to verify the inclusion of watermarks in comment bodies.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Enhance tests for DetectPotentialProblemsUseCase by mocking GitHub actions context to handle undefined SHA. This improves test reliability and ensures proper handling of commit context in potential problem detection.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Fix commit URL generation to properly encode owner and repository names. Added tests to verify URL encoding for special characters in commit links.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Fix commit URL generation in CLI and GitHub action files to properly encode owner and repository names, ensuring correct handling of special characters in URLs.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Enhance publishFindings tests to validate commitSha handling in comments and overflow scenarios. Added cases for using commitSha as a watermark, passing it to addComment and updateComment, and ensuring correct behavior when findings lack associated files. Improved test coverage for comment creation logic in various conditions.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Refactor publishFindings to improve commitSha handling in comments. Updated logic to ensure correct behavior in scenarios with missing associated files and added tests for various conditions, enhancing overall test coverage.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Enhance ContentInterface tests to improve error handling and logging. Added test cases for scenarios where extraction and update operations throw errors, ensuring that errors are logged appropriately and that the functions return undefined as expected. This improves the robustness of the content handling logic.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Enhance logging and error handling across various use cases. Introduced logDebugInfo for detailed execution tracing, added logWarn for non-critical warnings, and improved error messages for better context. Updated tests to mock new logging functions, ensuring comprehensive coverage of logging behavior.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Enhance logging in mainRun function for GitHub Action and CLI. Added detailed log messages for execution events, setup completion, and action handling, improving traceability and debugging. Removed unused truncate function and adjusted error handling for JSON parsing to log full response text for better context.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Update pull request description template to clarify output format requirements. Removed unnecessary preamble and commentary instructions, ensuring a more concise and structured output for PR descriptions.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Update pull request description template in CLI and GitHub Action to streamline output format. Clarified instructions to eliminate preamble and commentary, ensuring a more direct and structured presentation of PR descriptions.
  • bugfix-314-error-merging-release-branch-after-successful-deployment: Enhance logging functionality by introducing a sanitizeLogMessage function to remove markdown code fences from log messages. This ensures log output remains clear and unbroken when visualized in environments like GitHub Actions. Updated logInfo, logWarn, logError, and logDebugInfo functions to utilize the new sanitization method. Added tests to verify that markdown code fences are stripped from log messages.
  • Merge pull request [#314] 🐛 - Error merging release branch after successful deployment #315 from vypdev/bugfix/314-error-merging-release-branch-after-successful-deployment

[#314] 🐛 - Error merging release branch after successful deployment

  • gh-action: updated compiled files and bumped version to 2.0.3
  • Merge branch 'release/2.0.3' of https://github.com/vypdev/copilot into release/2.0.3
  • release-2.0.3: updated compiled files

This PR was automatically created by copilot.

efraespada and others added 21 commits February 15, 2026 13:14
Merge release/2.0.2 into develop
…Enhance documentation and implementation for deploy label and merge flow. Added new sections in README and index.mdx, and improved MergeRepository to wait for PR-specific check runs before merging. Updated tests for MergeRepository and DeployedActionUseCase to cover new behavior and ensure correctness in handling merges and check waits.
…Enhance MergeRepository and DeployedActionUseCase documentation to clarify PR-specific check run handling and deployment flow. Updated comments and type definitions to reflect new behavior, ensuring better understanding of the merging process and check wait logic.
…Enhance MergeRepository to handle fallback to status checks when no PR-specific check runs are available after polling. Added test case to verify that the merge process correctly waits for pending status checks before proceeding. This improves the robustness of the merging logic and ensures proper handling of check statuses.
…Enhance logging functionality by introducing accumulated log management. Added methods to clear and retrieve accumulated logs, and updated log functions to support accumulation. Implemented tests to verify the correct behavior of log accumulation and formatting, ensuring robust logging capabilities.
…Enhance IssueRepository and publishFindings functionality to support commit SHA watermarks in comments. Updated addComment and updateComment methods to accept an options parameter for commitSha, allowing comments to include a link to the specific commit. Adjusted related tests to verify the inclusion of watermarks in comment bodies.
…Enhance tests for DetectPotentialProblemsUseCase by mocking GitHub actions context to handle undefined SHA. This improves test reliability and ensures proper handling of commit context in potential problem detection.
…Fix commit URL generation to properly encode owner and repository names. Added tests to verify URL encoding for special characters in commit links.
…Fix commit URL generation in CLI and GitHub action files to properly encode owner and repository names, ensuring correct handling of special characters in URLs.
…Enhance publishFindings tests to validate commitSha handling in comments and overflow scenarios. Added cases for using commitSha as a watermark, passing it to addComment and updateComment, and ensuring correct behavior when findings lack associated files. Improved test coverage for comment creation logic in various conditions.
…Refactor publishFindings to improve commitSha handling in comments. Updated logic to ensure correct behavior in scenarios with missing associated files and added tests for various conditions, enhancing overall test coverage.
…Enhance ContentInterface tests to improve error handling and logging. Added test cases for scenarios where extraction and update operations throw errors, ensuring that errors are logged appropriately and that the functions return undefined as expected. This improves the robustness of the content handling logic.
…Enhance logging and error handling across various use cases. Introduced logDebugInfo for detailed execution tracing, added logWarn for non-critical warnings, and improved error messages for better context. Updated tests to mock new logging functions, ensuring comprehensive coverage of logging behavior.
…Enhance logging in mainRun function for GitHub Action and CLI. Added detailed log messages for execution events, setup completion, and action handling, improving traceability and debugging. Removed unused truncate function and adjusted error handling for JSON parsing to log full response text for better context.
…Update pull request description template to clarify output format requirements. Removed unnecessary preamble and commentary instructions, ensuring a more concise and structured output for PR descriptions.
…Update pull request description template in CLI and GitHub Action to streamline output format. Clarified instructions to eliminate preamble and commentary, ensuring a more direct and structured presentation of PR descriptions.
…Enhance logging functionality by introducing a sanitizeLogMessage function to remove markdown code fences from log messages. This ensures log output remains clear and unbroken when visualized in environments like GitHub Actions. Updated logInfo, logWarn, logError, and logDebugInfo functions to utilize the new sanitization method. Added tests to verify that markdown code fences are stripped from log messages.
…branch-after-successful-deployment

[#314] 🐛 - Error merging release branch after successful deployment
@vypbot vypbot linked an issue Feb 17, 2026 that may be closed by this pull request
@vypbot vypbot merged commit b58aee7 into master Feb 17, 2026
@docs-page
Copy link

docs-page bot commented Feb 17, 2026

To view this pull requests documentation preview, visit the following URL:

docs.page/vypdev/copilot~317

Documentation is deployed and generated using docs.page.

@codecov-commenter
Copy link

Codecov Report

❌ Patch coverage is 88.70293% with 27 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.87%. Comparing base (b80d67c) to head (418429b).
⚠️ Report is 40 commits behind head on master.

Files with missing lines Patch % Lines
src/usecase/actions/check_progress_use_case.ts 44.44% 2 Missing and 3 partials ⚠️
src/actions/github_action.ts 78.57% 0 Missing and 3 partials ⚠️
...usecase/steps/issue/link_issue_project_use_case.ts 62.50% 2 Missing and 1 partial ⚠️
...pull_request/link_pull_request_project_use_case.ts 62.50% 2 Missing and 1 partial ⚠️
src/data/repository/ai_repository.ts 87.50% 0 Missing and 2 partials ⚠️
...case/steps/issue/remove_issue_branches_use_case.ts 60.00% 1 Missing and 1 partial ⚠️
src/actions/common_action.ts 95.45% 0 Missing and 1 partial ⚠️
.../steps/commit/check_changes_issue_size_use_case.ts 0.00% 0 Missing and 1 partial ⚠️
...teps/commit/notify_new_commit_on_issue_use_case.ts 0.00% 0 Missing and 1 partial ⚠️
...usecase/steps/common/check_permissions_use_case.ts 66.66% 0 Missing and 1 partial ⚠️
... and 5 more
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #317      +/-   ##
==========================================
+ Coverage   88.82%   90.87%   +2.05%     
==========================================
  Files         134      135       +1     
  Lines        5941     6171     +230     
  Branches     1272     1323      +51     
==========================================
+ Hits         5277     5608     +331     
+ Misses        250      170      -80     
+ Partials      414      393      -21     
Files with missing lines Coverage Δ
src/data/repository/issue_repository.ts 91.54% <100.00%> (+10.46%) ⬆️
src/data/repository/merge_repository.ts 92.30% <100.00%> (+2.45%) ⬆️
src/prompts/update_pull_request_description.ts 100.00% <ø> (ø)
src/usecase/actions/create_release_use_case.ts 100.00% <100.00%> (ø)
src/usecase/actions/create_tag_use_case.ts 100.00% <100.00%> (ø)
src/usecase/actions/deployed_action_use_case.ts 100.00% <ø> (ø)
src/usecase/actions/recommend_steps_use_case.ts 97.22% <100.00%> (+0.16%) ⬆️
src/usecase/single_action_use_case.ts 69.04% <100.00%> (+0.75%) ⬆️
...ase/steps/commit/bugbot/bugbot_autofix_use_case.ts 94.87% <100.00%> (+0.27%) ⬆️
...commit/bugbot/detect_bugbot_fix_intent_use_case.ts 93.75% <100.00%> (+0.20%) ⬆️
... and 27 more

... and 7 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🚀🧑‍💻 - 2.0.3 - Debug logs and prompt improvements

3 participants

Comments