Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update versions #10

Merged
merged 1 commit into from
Jan 5, 2024
Merged

chore: update versions #10

merged 1 commit into from
Jan 5, 2024

Conversation

zaripych
Copy link
Owner

@zaripych zaripych commented Jan 5, 2024

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Patch Changes

  • #7 5caf325 Thanks @zaripych! - fix: prevent pnpm from asking questions when install command is run

  • #6 b7ba5a3 Thanks @zaripych! - feat: this one introduces a feature which allows refactor-bot to perform aggregation and other more advanced analytics in the codebase

    We ask the model to generate a script for us that can use ts-morph directly and execute map/reduce in the repository. The script is ran in a separate process for a bit of safety and can also be moved to a Docker container.

  • #8 438ef72 Thanks @zaripych! - refactor: the caching layer of the refactor bot now supports events

    The events make it easier for separation of concerns between modules.

    For example, it now allows us to collect refactor results from multiple layers of code without having to pass around mutable references.

    This also allows us to measure the performance of the refactor bot and calculate the costs associated with OpenAI api.

    All of this to prepare for the refactor bot to have automatically evaluate itself and setup benchmarks that could be used to further measure and improve it's performance.

  • #2 2d7df8e Thanks @zaripych! - fix: sanitised result of the functions to exclude user's repository path from the output of the functions

  • #2 b04ab6b Thanks @zaripych! - fix: introduced a parameter which allows us to control how TypeScript projects are loaded in monorepo scenarios

    Ie if useCombinedTsMorphProject is true then the original strategy is used - where we load all TypeScript projects into a single ts-morph Project. This allows cross-project references to be easily found and traced. The disadvantage of this approach is that it might not just work if projects settings are different.

  • #7 5caf325 Thanks @zaripych! - fix: format function would leave one variable unformatted when it is preceeded with an empty string

  • #7 5caf325 Thanks @zaripych! - fix: the references function would return empty array when includeFilePaths parameter is used for a node built-in

  • #3 401d3b5 Thanks @zaripych! - fix: the package manager not being determined correctly if "packageManager" field is specified in the package.json

  • #4 ef77b8d Thanks @zaripych! - fix: formatting going to infinite cycle if the values contain placeholders

  • #2 b65fe19 Thanks @zaripych! - fix: module imports function is now smarter and doesn't include results from in-repo modules that import themselves

    This should ensure that when we _ are looking for imports of "package" where the "package" _ is one of the monorepo packages - we do not include itself importing its own internal files.

  • #2 b04ab6b Thanks @zaripych! - fix: added new GPT4 models to the list of possible choices

@zaripych zaripych merged commit 8f1a3da into main Jan 5, 2024
2 checks passed
@zaripych zaripych deleted the changeset-release/main branch January 5, 2024 11:54
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.

1 participant