Skip to content

Conversation

@pelikhan
Copy link
Contributor

Refresh the dependency versions in the project to ensure compatibility and access to the latest features and fixes.

@pelikhan pelikhan marked this pull request as ready for review August 14, 2025 15:53
@dsyme dsyme merged commit 0c1dee4 into main Aug 14, 2025
6 checks passed
@dsyme dsyme deleted the go_mod_updates branch August 14, 2025 15:57
pelikhan added a commit that referenced this pull request Sep 4, 2025
* Make missing-tool safe output optional instead of always enabled by default (#53)

* Initial plan

* Implement missing-tool safe output for reporting unavailable functionality

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

* Make missing-tool safe output optional instead of always enabled

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

* Optimize frontmatter error location detection with sub-YAML search for nested additional properties (#50)

* Remove GITHUB_TOKEN usage from format-and-commit workflow

* Initial plan

* Improve frontmatter error source location logic for additional properties and offsets

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

* Enhance nested additional properties error location handling

- Modified LocateJSONPathInYAMLWithAdditionalProperties to handle additional properties in nested objects
- Added findAdditionalPropertyInNestedContext function to locate properties within specific JSON path contexts
- Added findNestedSection function to identify YAML sections corresponding to JSON paths
- Added comprehensive test coverage for nested additional properties scenarios
- Maintains backward compatibility with existing root-level additional properties handling

Fixes handling of errors like "at '/on': additional properties 'foobar' not allowed" to point to exact location of 'foobar' rather than the 'on:' line.

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

* Optimize nested additional properties search for JSON paths

When a JSON path is available, search within sub-YAML content instead of entire YAML:
- Extract the YAML content for the specific JSON path section
- Normalize indentation for the sub-content
- Perform additional property search within the extracted sub-YAML
- Map coordinates back to original YAML positions

This improves efficiency by avoiding searches through unrelated YAML sections and provides more precise error location detection as requested in feedback.

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

---------

Co-authored-by: Peli de Halleux <pelikhan@users.noreply.github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

* Add support for custom environment variables in engine configuration using GitHub Actions syntax (#56)

* Initial plan

* Add support for custom environment variables in engine configuration

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

* Change env field type from array to map for GitHub Actions compatibility

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: Peli de Halleux <pelikhan@users.noreply.github.com>

* Add missing tool reporting functionality to workflow and update documentation

* Add missing tool reporting functionality to workflow and update documentation

---------

Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
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.

3 participants