microsoft/semantic-kernel
1
0
Fork 0
mirror of https://github.com/microsoft/semantic-kernel.git synced 2026-10-12 11:19:56 +00:00
Code Issues Packages Projects Releases Wiki Activity
961 Commits 64 Branches 1,077 Tags
java-0.2.1-beta-test
Commit Graph
961 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
GitHub f8c4067571 [maven-release-plugin] prepare release java-0.2.1-beta java-0.2.1-beta-test 2023-07-06 21:34:50 +01:00
John Oliver 1ee67c3d21 Bump versions 2023-07-06 21:33:53 +01:00
GitHub bbf9d1742e [maven-release-plugin] prepare for next development iteration 2023-07-06 21:06:52 +01:00
GitHub 9f8291d366 [maven-release-plugin] prepare release java-0.2.0-beta 2023-07-06 21:06:52 +01:00
John Oliver 643ae267ab Prepare pom for release 2023-07-06 21:04:41 +01:00
David GrieveLuigi Montoyajoe-braleyLuigi96Mark WallaceJohn Oliver
 		a1749f78b4 Java: Connectors - Memory - Unit test coverage #1598 (#1795) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->
Java: Connectors - Memory - Unit test coverage #1598 

### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->
Run unit tests with coverage and add additional tests to try to increase
coverage.
Added positive tests cases for AzureCognitiveSearchMemory. Negative
tests and coverage need to be addressed.
Because this is somewhat time consuming, I suggest that be done in a
separate PR rather than hold this PR.
I have created [Java: Increase coverage of
AzureCognitiveSearchMemoryTests
](https://github.com/microsoft/semantic-kernel/issues/1797) for that
purpose.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [ x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄

---------

Co-authored-by: Luigi Montoya <[email protected]>
Co-authored-by: joe-braley <[email protected]>
Co-authored-by: Luigi96 <[email protected]>
Co-authored-by: Mark Wallace <[email protected]>
Co-authored-by: John Oliver <[email protected]>
 2023-07-05 18:50:03 +01:00
John Oliver 152593ea03 Java: Add sequential planner (#1526) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->


### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->


### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [ ] The code builds clean without any errors or warnings
- [ ] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [ ] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [ ] All unit tests pass, and I have added new tests where possible
- [ ] I didn't break anyone 😄
 2023-07-05 18:34:56 +01:00
markwallace-microsoft 5447c1eb86 Merge remote-tracking branch 'origin' into experimental-java 2023-07-03 09:24:38 +01:00
Yoshio Terada a80611bd9a Java: Http skill Added (#1712) 
Added HttpSkill for Java

### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->

Based on the
[http_skill.py](https://github.com/microsoft/semantic-kernel/blob/main/python/semantic_kernel/core_skills/http_skill.py)

I implemented the Http Skill by using Mono of Project Reactor.
And I implemented the Test code with Mock.

### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->


### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [ ] The code builds clean without any errors or warnings
- [ ] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [ ] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [ ] All unit tests pass, and I have added new tests where possible
- [ ] I didn't break anyone 😄
 2023-07-03 09:23:00 +01:00
Desmond Howard 3105aa13d9 Copilot Chat: align bash deploy-webapi script with powershell (#1786) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->
I noticed the script was slightly misaligned during my deployment of
webapi.

### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->
corrects the usage string and sets a default value for the
`PACKAGE_FILE_PATH` similar to the Powershell script.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [X] The code builds clean without any errors or warnings
- [X] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [X] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [X] All unit tests pass, and I have added new tests where possible
- [X] I didn't break anyone 😄
 2023-06-30 20:56:21 +00:00
Desmond Howard cd5120fa18 Copilot Chat: Fix ESLint violations + enable linter during build (#1710) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->
fix the ESLint violations in CopilotChat and enable the linter to run
during `yarn start`/`yarn build`.

**lint errors going forward will fail the build** and will need to be
corrected before a PR can merge.
we have already configured the linter to auto-fix on save in VSCode and
for other IDEs the `yarn lint:fix` script can be used.

### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->
- `.node-pr.yml`: removed unneeded directory filter since `samples/apps`
no longer contains a `yarn.lock`.
- `.vscode/settings.json`: updated to point to the `eslintConfig` in the
`package.json` rather than the shared JS file. this is required so that
the plugins are resolved correctly by the extension.
- `.eslintrc.js`:
  - removed deprecated `@typescript-eslint` rules.
  - removed plugins already resolved from create-react-app.
- removed `standard-with-typescript` extended config in favor of more
widely used configs.
- `webapp/package.json`: 
- pinned TS version to `5.0.4`, the latest version below `5.1.0`. this
is a dependency requirement of `@typescript-eslint` and otherwise the
linter will not work.
- re-added `eslintConfig` that now extends from the `../../eslintrc.js`.
this is required so that the plugins are resolved correctly by ESLint.
- `samples/apps/package.json`: 
- deleted since there are now no shared dependencies that need to be
downloaded.
  - similarly, the `yarn.lock` file was removed as well. 
- all of the plugins/configs used in `.eslintrc.js` are already included
in the [create-react-app
config](https://github.com/facebook/create-react-app/blob/main/packages/eslint-config-react-app/index.js)
which we extend.
- **all other files**: fixed **379** errors and **42** warnings.

### Preview
#### During build
<img width="258" alt="image"
src="https://github.com/microsoft/semantic-kernel/assets/52973358/94a42909-7cb6-48a7-8d5f-6f55a15d6025">

#### In VSCode w/ ESLint extension installed
<img width="253" alt="image"
src="https://github.com/microsoft/semantic-kernel/assets/52973358/182604ab-6228-49f6-8983-4ef902e7e945">

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [X] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [X] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [X] All unit tests pass, and I have added new tests where possible
- [X] I didn't break anyone 😄
- [X] Bugbash to double check nothing is broken (not yet but before
merging)
 2023-06-30 19:19:11 +00:00
Dmytro Struk 348c1c8f2b Chroma - fix for saving same memory record multiple times (#1790) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->
Method `SaveInformationAsync` of kernel memory type should be idempotent
to update memory record with same key multiple times. This PR contains
changes to allow that behavior in Chroma connector and tests to verify
it.

### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->
1. Replaced Chroma `POST /collections/{collection_id}/add` with `POST
collections/{collection_id}/upsert` to allow idempotent behavior.
2. Added integration tests to verify scenario with adding/updating
memory record with same key multiple times.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
 2023-06-30 16:36:07 +00:00
Teresa Hoang a3731645bc Copilot Chat: Adding missing appsettings chatparticipant config to bicep template (#1780) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->
Adding `ChatStore:Cosmos:ChatParticipantsContainer` config setting to
the bicep template for the web app.
In response to:
https://github.com/orgs/microsoft/projects/852/views/5?pane=issue&itemId=32088282

Did a test deployment and verified that new setting is in the config! 
 {

    "name": "ChatStore:Cosmos:ChatParticipantsContainer",
    "value": "chatparticipants",
    "slotSetting": false

  },
  

![image](https://github.com/microsoft/semantic-kernel/assets/125500434/4dba7793-2847-4435-98f9-5f7750f8b87f)

Then tested deployed webapi with local webapp instance and chatbot is
running as expected
  
### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
 2023-06-30 14:27:09 +00:00
Adrián PanellaandShawn Callegari 5cae285401 Python: add iso_date time skill (#1501) 
Date might be affected by locale language.
For some use cases is better to have a fixed and structured format

Co-authored-by: Shawn Callegari <[email protected]>
 2023-06-29 20:40:56 +00:00
Henri SchulteandAman Sachan 20dee6dbf0 Python: Correct syntax in core skill examples (#1731) 
Fix for #1730 
Some core skills include example code showing how to import the skill.
Some of these examples, used an invalid syntax where arguments were in
the reversed order, e.g. kernel.import_skill("wait", WaitSkill());
instead of the valid kernel.import_skill(WaitSkill(), "wait").

---------

Co-authored-by: Aman Sachan <[email protected]>
 2023-06-29 20:21:37 +00:00
dependabot[bot]andShawn Callegari 57b7f09e4b Bump Microsoft.Azure.Functions.Worker from 1.14.1 to 1.15.0 in /dotnet (#1721) 
Bumps
[Microsoft.Azure.Functions.Worker](https://github.com/Azure/azure-functions-dotnet-worker)
from 1.14.1 to 1.15.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/Azure/azure-functions-dotnet-worker/releases">Microsoft.Azure.Functions.Worker's
releases</a>.</em></p>
<blockquote>
<h2>Microsoft.Azure.Functions.Worker 1.15.0-preview1</h2>
<h2>What's Changed</h2>
<h3>Microsoft.Azure.Functions.Worker (metapackage)</h3>
<ul>
<li>Update Microsoft.Azure.Functions.Worker.Core dependency to
1.13.0-preview1</li>
<li>Update Microsoft.Azure.Functions.Worker.Grpc dependency to
1.11.0-preview1</li>
</ul>
<h3>Microsoft.Azure.Functions.Worker.Core 1.13.0-preview1</h3>
<ul>
<li>Implementation for bypass deferred binding (<a
href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1462">#1462</a>/<a
href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1495">#1495</a>)</li>
</ul>
<h3>Microsoft.Azure.Functions.Worker.Grpc 1.11.0-preview1</h3>
<ul>
<li>Implementation for bypass deferred binding (<a
href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1462">#1462</a>/<a
href="https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/1495">#1495</a>)</li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/Azure/azure-functions-dotnet-worker/compare/1.14.1...1.15.0-preview1">https://github.com/Azure/azure-functions-dotnet-worker/compare/1.14.1...1.15.0-preview1</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/Azure/azure-functions-dotnet-worker/commits">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=Microsoft.Azure.Functions.Worker&package-manager=nuget&previous-version=1.14.1&new-version=1.15.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Shawn Callegari <[email protected]>
 2023-06-29 20:12:32 +00:00
Tara WLee MillerCasey SchadewitzcschadewitzAbby HarrisonDevis LucatoDmytro StrukShawn Callegari
 		3f092e1487 Creating Pinecone memory store for Python (#769) 
### Motivation and Context
Adding a Pinecone Memory store using the Pinecone vector database client
for SK python

  Add Pinecone vector db memory to SK Python

  Memory storage for SK and vectors

### Description
- Using the existing pinecone python module/client
- Reviewing with console exceptions responses that come back from
pinecone, will update if any were omitted
- Currently investigating and would like feedback if I should respond to
throttling errors in a different manner
- Currently testing each API response, slight delay may occur due to
throttling of my starter account in Pinecone.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [ ] The code builds clean without any errors or warnings
- [X] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [ ] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [ ] All unit tests pass, and I have added new tests where possible
- [X] I didn't break anyone 😄

---------

Co-authored-by: Lee Miller <[email protected]>
Co-authored-by: Casey Schadewitz <[email protected]>
Co-authored-by: cschadewitz <[email protected]>
Co-authored-by: Abby Harrison <[email protected]>
Co-authored-by: Devis Lucato <[email protected]>
Co-authored-by: Dmytro Struk <[email protected]>
Co-authored-by: Shawn Callegari <[email protected]>
 2023-06-29 20:09:58 +00:00
dependabot[bot] a335fbf9d6 Bump numpy from 1.24.3 to 1.24.4 in /python (#1723) 
Bumps [numpy](https://github.com/numpy/numpy) from 1.24.3 to 1.24.4.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/numpy/numpy/releases">numpy's
releases</a>.</em></p>
<blockquote>
<h2>v1.24.4</h2>
<h1>NumPy 1.24.4 Release Notes</h1>
<p>NumPy 1.24.4 is a maintenance release that fixes a few bugs
discovered after the 1.24.3 release. It is the last planned
release in the 1.24.x cycle. The Python versions supported by
this release are 3.8-3.11.</p>
<h2>Contributors</h2>
<p>A total of 4 people contributed to this release. People with a
&quot;+&quot; by
their names contributed a patch for the first time.</p>
<ul>
<li>Bas van Beek</li>
<li>Charles Harris</li>
<li>Sebastian Berg</li>
<li>Hongyang Peng +</li>
</ul>
<h2>Pull requests merged</h2>
<p>A total of 6 pull requests were merged for this release.</p>
<ul>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/23720">#23720</a>:
MAINT, BLD: Pin rtools to version 4.0 for Windows builds.</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/23739">#23739</a>:
BUG: fix the method for checking local files for 1.24.x</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/23760">#23760</a>:
MAINT: Copy rtools installation from install-rtools.</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/23761">#23761</a>:
BUG: Fix masked array ravel order for A (and somewhat K)</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/23890">#23890</a>:
TYP,DOC: Annotate and document the <code>metadata</code> parameter
of...</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/23994">#23994</a>:
MAINT: Update rtools installation</li>
</ul>
<h2>Checksums</h2>
<h3>MD5</h3>
<pre><code>25049e3aee79dde29e7a498d3ad13379
numpy-1.24.4-cp310-cp310-macosx_10_9_x86_64.whl
579b5c357c918feaef4af03af8afb721
numpy-1.24.4-cp310-cp310-macosx_11_0_arm64.whl
c873a14fa4f0210884db9c05e2904286
numpy-1.24.4-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
110a13ac016286059f0658b52b3646c0
numpy-1.24.4-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
fa67218966c0aef4094867cad7703648  numpy-1.24.4-cp310-cp310-win32.whl
6ee768803d8ebac43ee0a04e628a69f9  numpy-1.24.4-cp310-cp310-win_amd64.whl
0c918c16b58cb7f6773ea7d76e0bdaff
numpy-1.24.4-cp311-cp311-macosx_10_9_x86_64.whl
20506ae8003faf097c6b3a8915b4140e
numpy-1.24.4-cp311-cp311-macosx_11_0_arm64.whl
902df9d5963e89d88a1939d94207857f
numpy-1.24.4-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
2543611d802c141c8276e4868b4d9619
numpy-1.24.4-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
37b23a4e4e148d61dd3a515ac5dbf7ec  numpy-1.24.4-cp311-cp311-win32.whl
25e9f6bee2b65ff2a87588e717f15165  numpy-1.24.4-cp311-cp311-win_amd64.whl
f39a0cc3655a482af7d300bcaff5978e
numpy-1.24.4-cp38-cp38-macosx_10_9_x86_64.whl
9ed27941388fdb392e8969169f3fc600
numpy-1.24.4-cp38-cp38-macosx_11_0_arm64.whl
dee3f0c7482f1dc8bd1cd27b9b028a2c
numpy-1.24.4-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
2cc0967af29df3caef9fb3520f14e071
numpy-1.24.4-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
8572a3a0973fa78355bcb5f737745b47  numpy-1.24.4-cp38-cp38-win32.whl
</code></pre>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/numpy/numpy/commit/9315a9072b2636f75c831b4eca9f42a5f67ca2fb"><code>9315a90</code></a>
Merge pull request <a
href="https://redirect.github.com/numpy/numpy/issues/24044">#24044</a>
from charris/fix-simple-anaconda-client</li>
<li><a
href="https://github.com/numpy/numpy/commit/334c25ef9508d43e0e2b1a3a8fb71fb5ab9338db"><code>334c25e</code></a>
BLD: Use urllib &lt; 2.0.0 for anaconda-client.</li>
<li><a
href="https://github.com/numpy/numpy/commit/008b17fd45c5d1c91da78964825388205bc9f821"><code>008b17f</code></a>
Merge pull request <a
href="https://redirect.github.com/numpy/numpy/issues/24040">#24040</a>
from charris/prepare-1.24.4-release</li>
<li><a
href="https://github.com/numpy/numpy/commit/7162cd61ea8924c015e90e5cbb9f079aa7d89e2a"><code>7162cd6</code></a>
REL: Prepare for the NumPy 1.24.4 release</li>
<li><a
href="https://github.com/numpy/numpy/commit/2d2774730ddc9b20edc8237e3ccc5f95f67e808f"><code>2d27747</code></a>
Merge pull request <a
href="https://redirect.github.com/numpy/numpy/issues/23994">#23994</a>
from charris/update-rtools-install</li>
<li><a
href="https://github.com/numpy/numpy/commit/878122c0235745c7728fcac8c1d2363841c28993"><code>878122c</code></a>
MAINT: Update rtools installation</li>
<li><a
href="https://github.com/numpy/numpy/commit/a5f33ab3bcfdf463dcefdb1c044f0bdd98c5301d"><code>a5f33ab</code></a>
Merge pull request <a
href="https://redirect.github.com/numpy/numpy/issues/23890">#23890</a>
from charris/backport-23887</li>
<li><a
href="https://github.com/numpy/numpy/commit/d62280dace6b773b7f54826dbfbd4d6375134fff"><code>d62280d</code></a>
DOC: Document the <code>metadata</code> parameter of the
<code>dtype</code> constructor</li>
<li><a
href="https://github.com/numpy/numpy/commit/6da40bb23a0eb94a70186522924d753ee5d4c476"><code>6da40bb</code></a>
TYP: Add annotations for the <code>np.dtype</code> metadata
parameter</li>
<li><a
href="https://github.com/numpy/numpy/commit/553bb3fe58e606ee257765cad526be479178f643"><code>553bb3f</code></a>
Merge pull request <a
href="https://redirect.github.com/numpy/numpy/issues/23761">#23761</a>
from charris/backport-23680</li>
<li>Additional commits viewable in <a
href="https://github.com/numpy/numpy/compare/v1.24.3...v1.24.4">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=numpy&package-manager=pip&previous-version=1.24.3&new-version=1.24.4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
 2023-06-29 20:07:57 +00:00
JadynandDmytro Struk 07aa6a73d5 Re-implementing the Postgres memory store (#1735) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->
Reimplement Postgres in-memory storage based on the discussion in #1338.


### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->
- Re-implementing the Postgres memory store, mapping between SK
collection to Postgres table.
- PostgresMemoryStore no longer implements `IDisposable` pattern.
- No longer execute the enable pgvector extension statement, add it to
README.md to be executed by the user. It only needs to be executed once
in the database, and the extension may be enabled differently for
different hosting methods.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄

---------

Co-authored-by: Dmytro Struk <[email protected]>
 2023-06-29 20:02:36 +00:00
Mark Wallace 537bc497a1 Fix to use semantic function default values (#1772) 
### Motivation and Context

Please help reviewers and future users, providing the following
information:
1. Why is this change required? Default values specified in a semantic
function config.json are not being used when executing the semantic
function


### Description

1. Add logic to use default values when executing a semantic function
2. Add a new extension method to allow execution of the text prompt

### Contribution Checklist

- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
 2023-06-29 19:56:01 +00:00
Shawn Callegari 16d52c155a Update and rename dotnet-ci.yml to dotnet-ci-windows.yml dotnet-0.17.230629.1-preview 2023-06-28 18:31:42 -07:00
N. Taylor MullenandShawn Callegari 6a370e7d13 Fix SKFunction.InvokeAsync to respect input when passed in explicitly. (#1757) 
- The defaults for `mutableContext` are `true` which make it super easy
to fall into this trap. I slammed my head against the wall for a while
until realizing that the SK InvokeAsync method wasn't properly utilizing
the `input` parameter.

---------

Co-authored-by: Shawn Callegari <[email protected]>
 2023-06-29 01:25:59 +00:00
Mark KarleandMark Karle de9c202a72 Reverting torch to 2.0.0 (#1761) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->
[Integration tests were
failing](https://github.com/microsoft/semantic-kernel/actions/runs/5400873036)
due to a problem importing torch. This might be a mismatch in torch and
cuda dependencies. Reverting torch to 2.0.0 led to successful
integration tests here:
https://github.com/mkarle/semantic-kernel/actions/runs/5405696396

### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->
- Locally, I reverted torch to 2.0.0 and integration tests succeeded
- Then, I upgraded torch back to 2.0.1 and integration tests still
succeeded
- In my GitHub Actions, reverting to 2.0.0 succeeded:
https://github.com/mkarle/semantic-kernel/actions/runs/5405599455
- Upgrading back to 2.0.1 failed again, however:
https://github.com/mkarle/semantic-kernel/actions/runs/5405659136
- So now I've reverted back to 2.0.0 and they succeed:
https://github.com/mkarle/semantic-kernel/actions/runs/5405696396

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄

---------

Co-authored-by: Mark Karle <>
 2023-06-29 01:16:19 +00:00
Gina Triolo 6b2e38f89e Update input when invoking function with mutable context (#1768) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->
This change fixes #1443. There is a code path in
`SKFunctionExtensions.InvokeAsync` where we don't update the context
with the input from the user.

### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->
Update the `input` context variable before invoking the SK function, to
ensure the input gets passed through.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
 2023-06-29 01:15:55 +00:00
Devis Lucato d8ed339ed7 Update Memory Connectors feature matrix (#1759) 
* Add Chroma for Python
* Move up top Memory connectors with wider support
* Update Azure Search note
 2023-06-28 13:38:55 -07:00
SergeyMenshykhandDmytro Struk 032d6e7e36 OpenAPI fixes and improvements (#1737) 
### Motivation and Context
This PR ensures that the User-Agent is consistently passed for all
OpenAPI-related functionality, preventing rejections of HTTP requests by
Klarna ChatGPT plugin. It also introduces a data contract for the
RestApiOperation response, enabling reliable deserialization in SK
consumer code.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄

Co-authored-by: Dmytro Struk <[email protected]>
 2023-06-28 19:56:34 +00:00
Stephen Toub 7afbc20441 Consolidate duplicate HttpRequest files (#1739) 
### Motivation and Context

Move the HttpRequest helper into common files to avoid cloning the file
multiple times, the internally dedup the implemetations of the methods,
and improve the content creation to avoid a temporary string from json
serialization.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
 2023-06-28 19:53:50 +00:00
Gina Triolo d10fb879b0 Fixes for OpenApiSkillsExample (#1738) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->
Fix for issue #1336 - When the token limit is exceeded, we
unintentionally remove the system prompt from the chat history in order
to remain under the token limit. Also addresses a couple other small
issues with this sample.

### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->
- Remove chat history items beginning with index 1, so that the system
prompt (index 0) remains in the chat history.
- Fix a naming mismatch in the configuration - the code looks for
`TokenLimit` not `CompletionTokenLimit`
- Add `UserSecretsId` property to the csproj file so users won't need to
run `dotnet user-secrets init` themselves.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
 2023-06-28 16:35:34 +00:00
Stephen ToubandDmytro Struk 84e6fada0c Avoid recursion in TextChunker.BuildParagraph (#1709) 
### Motivation and Context

TextChunker.BuildParagraph is unnecessarily recursive and can lead to
stack overflows on large inputs.

### Description

Fixes https://github.com/microsoft/semantic-kernel/issues/1633

Also happens to make it more efficient with a few tweaks.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄

---------

Co-authored-by: Dmytro Struk <[email protected]>
 2023-06-27 22:09:20 +00:00
Lee Miller 823a4c7384 SequentialPlanner - Allow custom manual discovery and loading. (#1727) 
### Motivation and Context
This change is part of a need to enable planners that can reference a
large list of potential plugins that aren't loaded in a kernel instance.
Additionally, consumers of planners need to be able to load plugins on
demand when needed by a plan. The change includes some additional
improvements to the sequential plan parser and prompt.

Part of #1728 

### Description
This pull request refactors and improves the sequential plan parser and
config, simplifying the code, adding new features, and fixing some
issues. The main changes are:

- Use the Azure Chat Completion Service instead of the Azure Text
Completion Service for the sequential planner, and lower the relevancy
threshold for creating a plan. This allows for more flexibility and
creativity in generating plans, and improves the performance and
accuracy of the planner.
- Refactor the plan parsing logic to simplify the code and improve
readability. Remove unnecessary try-catch blocks, logging statements,
and string splitting logic. Reorder the parameters of the ToPlanFromXml
method to match the order of the XML attributes. Ignore text and comment
nodes in the plan XML, as they are not valid steps and could cause
confusion or errors. Remove the logic that adds empty nodes as steps, as
they are not valid functions and could cause errors or confusion.
- Add two optional functions to the SequentialPlannerConfig class that
allow the planner to use custom logic for getting available functions
and finding functions by name. These functions can be useful for
scenarios where the planner needs to access functions from different
sources or with different criteria, such as filtering by skill category
or function type. The default behavior of the planner remains unchanged
if these functions are not specified.
- Simplify and standardize the syntax for calling functions in the plan
XML, using fully qualified function names and consistent attribute names
for inputs, outputs, and parameters. Update the skprompt.txt file to
reflect the new syntax and add more instructions and examples for
creating a plan. Update the sequential plan parser tests to use the new
syntax and function names, and add a helper method to get the function
from the kernel context.
- Fix some minor typos and errors in the code and the skprompt.txt file.

Details:

-
dotnet/src/IntegrationTests/Planning/SequentialPlanner/SequentialPlannerTests.cs
- Changed the KernelSyntaxExamples and SequentialPlannerTests to use the
Azure Chat Completion Service instead of the Azure Text Completion
Service, by replacing the deployment name, endpoint, and key environment
variables.
- Removed the EmailSkillFake import from the InitializeKernel method, as
it is not used in any test case and is already imported in the
TestHelpers class.
- Updated the tests to reflect the changes in the plan parser and remove
the redundant or invalid steps. For example, remove the text and empty
nodes from the plan XML, and update the expected number and description
of the steps.
-
dotnet/src/Extensions/Planning.SequentialPlanner/SequentialPlanParser.cs
- Simplified the ToPlanFromXml method by removing unnecessary try-catch
blocks, logging statements, and string splitting logic.
- Reordered the parameters of the ToPlanFromXml method to match the
order of the XML attributes, as this makes the code more consistent and
easier to read.
- Ignored text and comment nodes in the plan XML, as they are not valid
steps and could cause confusion or errors. Added TODO comments for
possible future enhancements using text or comments as reasoning or
desired functions.
- Removed the logic that adds empty nodes as steps, as they are not
valid functions and could cause errors or confusion. Added TODO comments
for possible future enhancements using empty nodes as desired functions.
- Added a GetFunction parameter to the ToPlanFromXml method that takes a
delegate for finding a skill function by skill name and function name.
This delegate can be specified in the SequentialPlannerConfig class or
default to the existing logic of using the SKContext.
- Added a new static method GetFunction to the SequentialPlanParser
class that returns the default delegate for getting the ISKFunction
instance, which calls context.Skills.TryGetFunction.
- Fixed a minor typo in the GetFunctionName method, changing
"functionName" to "functionNameAttribute". This makes the code more
accurate and clear.
-
dotnet/src/Extensions/Planning.SequentialPlanner/SequentialPlannerConfig.cs
- Added a new property GetAvailableFunctionsAsync to the
SequentialPlannerConfig class that takes a delegate of type
Func<SequentialPlannerConfig, string,
Task<IOrderedEnumerable<FunctionView>>>. This delegate can be used to
provide a custom logic for retrieving available functions from a
semantic query, instead of using the default logic that calls
context.GetAvailableFunctionsAsync. The default value of this property
is null, which means the default logic will be used.
- Modified the SKContextSequentialPlannerExtensions class to use the
GetAvailableFunctionsAsync delegate if it is not null, otherwise fall
back to the default logic.
- dotnet/src/Extensions/Planning.SequentialPlanner/skprompt.txt
- Simplified and standardized the syntax for calling functions from
<function.{FunctionName} ... /> to
<function.{FullyQualifiedFunctionName} ... />, where
{FullyQualifiedFunctionName} is the name of the function with its
namespace or skill prefix, such as _GLOBAL_FUNCTIONS_.NovelOutline or
AuthorAbility.Summarize.


### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
 2023-06-27 19:03:34 +00:00
Tim SchaepsandGina Triolo b46ab22c63 updated copilot chat deployment readme based on learnings (#1711) 
### Motivation and Context
Thank you for this great addition where we can deploy the SK copilot
chat to an azure subscription. I went through the process and stumbled
into some issues. I updated the readme to solve those issues for others
that want to do the same... Additionally, I updated the deploy-webapp
ps1 and sh files to auto update the aad appregistration (set the
redirect uri to the newly deployed front end)


### Description
updated copilot chat deployment readme based on learnings:
1. I had to update my Azure CLI (a bit too old) as the deployment of the
webapp gave a strange error. I added a note that updating the CLI is a
good idea
2. To deploy the webapp, the readme only contained the bash command.
Since there is also a ps1 script available, I added the command to use
this one
3. updated both `deploy-webapp.ps1`and `deploy-webapp.sh` to ensure that
the AAD app registration is updated to auto redirect to the correct url
(webapp) and not show an nasty AAD error.

> small note, I tested the updated `deploy-webapp.ps1`, but bot the
`deploy-webapp.sh` as I did my deployment with powershell... should not
be a problem though as it is a call to the AZ CLI


### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄

---------

Co-authored-by: Gina Triolo <[email protected]>
 2023-06-27 16:23:29 +00:00
David GrieveLuigi Montoyajoe-braleyLuigi96Mark WallaceJohn Oliver
 		bc847731a4 Java: SemanticTextMemory#merge(MemoryQueryResult) (#1732) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->
This method was removed from the C# API. 
Issue [Java: Implement stubbed memory
code](https://github.com/microsoft/semantic-kernel/issues/1568)

### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->
Removed method from SemanticTextMemory interface and removed the
implementations. There was one use in
com.microsoft.semantickernel.planner.sequentialplanner.DefaultSequentialPlannerSKContext#rememberFunctionsAsync
which was replaced with a Flux#ignoreElements. This latter change was
vetted by @johnoliver

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] ~The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`~ Java code uses AOSP style
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄

---------

Co-authored-by: Luigi Montoya <[email protected]>
Co-authored-by: joe-braley <[email protected]>
Co-authored-by: Luigi96 <[email protected]>
Co-authored-by: Mark Wallace <[email protected]>
Co-authored-by: John Oliver <[email protected]>
 2023-06-27 15:30:30 +01:00
Yoshio Terada d6aa3d73b0 Java - Waitskill added (#1674) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->


### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->

Based on the
[wait_skill.py](https://github.com/microsoft/semantic-kernel/blob/main/python/semantic_kernel/core_skills/wait_skill.py)

I implemented the WaitSkill by using Mono of Project Reactor.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [ ] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
 2023-06-27 14:47:04 +01:00
Milder HernandezLuigi Montoyajoe-braleyLuigi96Mark WallaceJohn OliverDavid Grieve
 		1e781167fa Java: Add Timeskill (#1627) 
Add Timeskill

### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->


### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->


### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [ ] The code builds clean without any errors or warnings
- [ ] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [ ] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [ ] All unit tests pass, and I have added new tests where possible
- [ ] I didn't break anyone 😄

---------

Co-authored-by: Luigi Montoya <[email protected]>
Co-authored-by: joe-braley <[email protected]>
Co-authored-by: Luigi96 <[email protected]>
Co-authored-by: Mark Wallace <[email protected]>
Co-authored-by: John Oliver <[email protected]>
Co-authored-by: David Grieve <[email protected]>
 2023-06-27 14:43:54 +01:00
David GrieveLuigi Montoyajoe-braleyLuigi96Mark WallaceJohn Oliver
 		b7f7170a64 Java: Example14_SemanticMemory (#1355) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->
Port Example14_SemanticMemory.cs to Java

### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->
Port of Example14_SemanticMemory.cs to Java. 
This sample uses an Azure Cognitive Search connector, which was also
ported from dotnet/src/Connectors/Connectors.Memory.AzureCognitiveSearch
Changes needed to api and core modules. 

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] ~The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`~ Java code follows AOSP style
- [X] All unit tests pass, and I have added new tests where possible
- [X] I didn't break anyone 😄

---------

Co-authored-by: Luigi Montoya <[email protected]>
Co-authored-by: joe-braley <[email protected]>
Co-authored-by: Luigi96 <[email protected]>
Co-authored-by: Mark Wallace <[email protected]>
Co-authored-by: John Oliver <[email protected]>
 2023-06-27 13:02:53 +01:00
name 1efe78aab4 Fix SK-dotnet.sln Publish configuration 2023-06-26 20:24:44 -07:00
Lee MillerAlmir KazazicLee Miller
 		49e20107b9 Add StepwisePlanner extension for MRKL style planning (#1468) 
### Motivation and Context
This pull request adds a new extension for semantic planning using a
stepwise approach. The StepwisePlanner extension allows users to create
and execute plans that consist of a sequence of semantic and native
functions, each with a goal and a set of inputs and outputs. The
extension uses a semantic search engine to find relevant functions for
each step, and a plan creation service to generate a plan that satisfies
the user's ask. The extension also provides a system step function that
executes the plan and returns the final answer and intermediate
observations. The extension can be configured with various parameters,
such as the relevancy threshold, the maximum number of relevant
functions, the excluded and included functions and skills, and the
maximum number of tokens, iterations, and time for the plan.

Regarding #1472

### Description
- Add StepwisePlanner.cs, which registers the planner native functions
and the system step function
- Add StepwisePlannerConfig.cs, which defines the configuration options
for the StepwisePlanner extension
- Add SystemStep.cs, which represents a step in a Stepwise plan, with
properties for the thought, action, action variables, observation, final
answer, and original response
- Add helper methods for formatting and validating function views,
generating plan requests, and invoking the plan.
- Add logging and error handling for the planner extension
- Add unit tests for the planner extension and the native functions

### Related
- Majority of work initially started from @kaza in #992 

### Changes in other PRs to merge separately
- #1464
- #1465 
- #1466 

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄

---------

Co-authored-by: Almir Kazazic <[email protected]>

---------

Co-authored-by: Lee Miller <[email protected]>
dotnet-0.17.230626.1-preview 		2023-06-26 19:32:19 +00:00
Dmytro Struk 85d420f77c Chroma memory store - C# implementation (#1634) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->

This PR contains changes for Chroma C# memory store. 
For more information about Chroma, see:
https://docs.trychroma.com/getting-started.

To run integration tests, local Chroma server should be up and running.

To start local Chroma server for testing (this information is also
included in
[README](https://github.com/microsoft/semantic-kernel/blob/0fb77e0c0f347e3f22d79b3c99e7f84d35340462/dotnet/src/Connectors/Connectors.Memory.Chroma/README.md)):
1. Clone Chroma:

```bash
git clone https://github.com/chroma-core/chroma.git
cd chroma
```

2. Run local Chroma server with Docker within Chroma repository root:

```bash
docker-compose up -d --build
```

3. Use Semantic Kernel with Chroma, using server local endpoint
`http://localhost:8000`:
```csharp
const string endpoint = "http://localhost:8000";

ChromaMemoryStore memoryStore = new(endpoint);

IKernel kernel = Kernel.Builder
    .WithLogger(logger)
    .WithOpenAITextEmbeddingGenerationService("text-embedding-ada-002", "OPENAI_API_KEY")
    .WithMemoryStorage(memoryStore)
    //.WithChromaMemoryStore(endpoint) // This method offers an alternative approach to registering Chroma memory store.
    .Build();
```

### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->

Main public classes:
1. `ChromaMemoryStore` - implementation of `IMemoryStore` interface.
Uses `ChromaClient` to communicate with Chroma API. Throws
`ChromaMemoryStoreException` in case of issues.
2. `ChromaClient` - responsible for communication with Chroma API.
Throws `ChromaClientException` in case of issues.

Chroma entity models:
1. `ChromaCollectionModel` - defines Chroma collection.
2. `ChromaEmbeddingsModel` - defines Chroma embeddings, constructed from
`MemoryRecord`.
3. `ChromaQueryResultModel` - defines Chroma search result set.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [x] The code builds clean without any errors or warnings
- [x] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [x] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
 2023-06-26 19:24:30 +00:00
Alex ChaoAlex ChaoShawn Callegari
 		527d3782f8 [README] Add community calendar link to the main README (#1662) 
Adding the SK Community calendar to the main README for office hours and
community events

### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->


### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->


### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [ ] The code builds clean without any errors or warnings
- [ ] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [ ] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [ ] All unit tests pass, and I have added new tests where possible
- [ ] I didn't break anyone 😄

---------

Co-authored-by: Alex Chao <achao@achao>
Co-authored-by: Shawn Callegari <[email protected]>
 2023-06-25 23:05:11 +00:00
dependabot[bot]andShawn Callegari d90ee581fc Bump eslint-plugin-n from 16.0.0 to 16.0.1 in /samples/apps (#1708) 
Bumps
[eslint-plugin-n](https://github.com/eslint-community/eslint-plugin-n)
from 16.0.0 to 16.0.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/eslint-community/eslint-plugin-n/releases">eslint-plugin-n's
releases</a>.</em></p>
<blockquote>
<h2>Release 16.0.1</h2>
<ul>
<li>fix: Update all dependencies. Fix a few tests where eslint now
reports nodeType: null. (44cec62)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/eslint-community/eslint-plugin-n/commit/23ae4756e8e8cb988f41a6177fabba79751d55b2"><code>23ae475</code></a>
Release 16.0.1</li>
<li><a
href="https://github.com/eslint-community/eslint-plugin-n/commit/44cec62c4555c7855877cf8064bcf0d3338f4c95"><code>44cec62</code></a>
fix: Update all dependencies. Fix a few tests where eslint now reports
nodeT...</li>
<li>See full diff in <a
href="https://github.com/eslint-community/eslint-plugin-n/compare/16.0.0...16.0.1">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=eslint-plugin-n&package-manager=npm_and_yarn&previous-version=16.0.0&new-version=16.0.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Shawn Callegari <[email protected]>
 2023-06-25 22:50:03 +00:00
dependabot[bot]andShawn Callegari 40e7343de0 Bump @typescript-eslint/eslint-plugin from 5.59.11 to 5.60.0 in /samples/apps (#1697) 
Bumps
[@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin)
from 5.59.11 to 5.60.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/typescript-eslint/typescript-eslint/releases"><code>@​typescript-eslint/eslint-plugin</code>'s
releases</a>.</em></p>
<blockquote>
<h2>v5.60.0</h2>
<h1><a
href="https://github.com/typescript-eslint/typescript-eslint/compare/v5.59.11...v5.60.0">5.60.0</a>
(2023-06-19)</h1>
<h3>Features</h3>
<ul>
<li><strong>eslint-plugin:</strong> [restrict-plus-operands] add allow*
options (<a
href="https://redirect.github.com/typescript-eslint/typescript-eslint/issues/6161">#6161</a>)
(<a
href="https://github.com/typescript-eslint/typescript-eslint/commit/def09f88cdb4a85cebb8619b45931f7e2c88dfc0">def09f8</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md"><code>@​typescript-eslint/eslint-plugin</code>'s
changelog</a>.</em></p>
<blockquote>
<h1><a
href="https://github.com/typescript-eslint/typescript-eslint/compare/v5.59.11...v5.60.0">5.60.0</a>
(2023-06-19)</h1>
<h3>Features</h3>
<ul>
<li><strong>eslint-plugin:</strong> [restrict-plus-operands] add allow*
options (<a
href="https://redirect.github.com/typescript-eslint/typescript-eslint/issues/6161">#6161</a>)
(<a
href="https://github.com/typescript-eslint/typescript-eslint/commit/def09f88cdb4a85cebb8619b45931f7e2c88dfc0">def09f8</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/typescript-eslint/typescript-eslint/commit/c09b1c0252cbbf58e94ca5d671b6e05f29511144"><code>c09b1c0</code></a>
chore: publish v5.60.0</li>
<li><a
href="https://github.com/typescript-eslint/typescript-eslint/commit/def09f88cdb4a85cebb8619b45931f7e2c88dfc0"><code>def09f8</code></a>
feat(eslint-plugin): [restrict-plus-operands] add allow* options (<a
href="https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin/issues/6161">#6161</a>)</li>
<li>See full diff in <a
href="https://github.com/typescript-eslint/typescript-eslint/commits/v5.60.0/packages/eslint-plugin">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@typescript-eslint/eslint-plugin&package-manager=npm_and_yarn&previous-version=5.59.11&new-version=5.60.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Shawn Callegari <[email protected]>
 2023-06-25 22:45:08 +00:00
dependabot[bot]nameShawn Callegari
 		4c46c6121c Bump Microsoft.Extensions.DependencyInjection from 8.0.0-preview.4.23259.5 to 8.0.0-preview.5.23280.8 in /dotnet (#1460) 
Bumps
[Microsoft.Extensions.DependencyInjection](https://github.com/dotnet/runtime)
from 8.0.0-preview.4.23259.5 to 8.0.0-preview.5.23280.8.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/dotnet/runtime/releases">Microsoft.Extensions.DependencyInjection's
releases</a>.</em></p>
<blockquote>
<h2>.NET 8.0 Preview 5</h2>
<p><a
href="https://github.com/dotnet/core/releases/tag/v8.0.0-preview.5">Release</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/dotnet/runtime/commit/bc78804f5d1486bb7313d1661992626640091bf1"><code>bc78804</code></a>
[release/8.0-preview5] Use fully qualified type names for parameters and
don'...</li>
<li><a
href="https://github.com/dotnet/runtime/commit/90c32f64064b5fd0ac2b4b9ba5d471daac716c73"><code>90c32f6</code></a>
avoid breaking change (<a
href="https://redirect.github.com/dotnet/runtime/issues/86912">#86912</a>)</li>
<li><a
href="https://github.com/dotnet/runtime/commit/34ddd0615cb964b57779e69fd6192c855b82217c"><code>34ddd06</code></a>
Update dependencies from <a
href="https://github.com/dotnet/emsdk">https://github.com/dotnet/emsdk</a>
build 20230525.2 (<a
href="https://redirect.github.com/dotnet/runtime/issues/8">#8</a>...</li>
<li><a
href="https://github.com/dotnet/runtime/commit/f0d3ddc621e21029a750fa4238a590b1f7101cdd"><code>f0d3ddc</code></a>
[release/8.0-preview5] Bump net7 version to 7.0.7 (<a
href="https://redirect.github.com/dotnet/runtime/issues/86771">#86771</a>)</li>
<li><a
href="https://github.com/dotnet/runtime/commit/9ab19db8dc7bac7eccd11cd32176fde4c6da970f"><code>9ab19db</code></a>
Revert &quot;Update dependencies from <a
href="https://github.com/dotnet/icu">https://github.com/dotnet/icu</a>
build 20230524...</li>
<li><a
href="https://github.com/dotnet/runtime/commit/372e1a26fd8c11a12d1a8d6789cfdbe10afa01db"><code>372e1a2</code></a>
[release/8.0-preview5] Update dependencies from
dnceng/internal/dotnet-optimi...</li>
<li><a
href="https://github.com/dotnet/runtime/commit/86269be5108f14932a32de5dea5f41e5bec0a161"><code>86269be</code></a>
Update dependencies from <a
href="https://github.com/dotnet/emsdk">https://github.com/dotnet/emsdk</a>
build 20230524.3 (<a
href="https://redirect.github.com/dotnet/runtime/issues/8">#8</a>...</li>
<li><a
href="https://github.com/dotnet/runtime/commit/4db899f3cc4ad04818b5d5f1993e343b8b0afd34"><code>4db899f</code></a>
Update dependencies from <a
href="https://github.com/dotnet/icu">https://github.com/dotnet/icu</a>
build 20230524.1 (<a
href="https://redirect.github.com/dotnet/runtime/issues/86762">#86762</a>)</li>
<li><a
href="https://github.com/dotnet/runtime/commit/0e239f9b4d3057483bae6e2a168374d4dd2a2475"><code>0e239f9</code></a>
Add Microsoft.Extensions.Diagnostics.* to Aspnet Transport package (<a
href="https://redirect.github.com/dotnet/runtime/issues/86730">#86730</a>)</li>
<li><a
href="https://github.com/dotnet/runtime/commit/61d367b2d8c4ce364f7231b5a91898ed9435a990"><code>61d367b</code></a>
[mono][wasm] Fix support for virtual invokes. (<a
href="https://redirect.github.com/dotnet/runtime/issues/86709">#86709</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/dotnet/runtime/compare/v8.0.0-preview.4.23259.5...v8.0.0-preview.5.23280.8">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=Microsoft.Extensions.DependencyInjection&package-manager=nuget&previous-version=8.0.0-preview.4.23259.5&new-version=8.0.0-preview.5.23280.8)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: name <email>
Co-authored-by: Shawn Callegari <[email protected]>
 2023-06-25 22:35:17 +00:00
dependabot[bot]andShawn Callegari 59e8696942 Bump eslint from 8.42.0 to 8.43.0 in /samples/apps (#1699) 
Bumps [eslint](https://github.com/eslint/eslint) from 8.42.0 to 8.43.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/eslint/eslint/releases">eslint's
releases</a>.</em></p>
<blockquote>
<h2>v8.43.0</h2>
<h2>Features</h2>
<ul>
<li><a
href="https://github.com/eslint/eslint/commit/14581ff15aaee5a55c46bbf4983818ddc8dd7cb1"><code>14581ff</code></a>
feat: directive prologue detection and autofix condition in
<code>quotes</code> (<a
href="https://redirect.github.com/eslint/eslint/issues/17284">#17284</a>)
(Francesco Trotta)</li>
<li><a
href="https://github.com/eslint/eslint/commit/e50fac3f8f998f729e3080e256066db3a7827c67"><code>e50fac3</code></a>
feat: add declaration loc to message in block-scoped-var (<a
href="https://redirect.github.com/eslint/eslint/issues/17252">#17252</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/1b7faf0702b1af86b6a0ddafc37cf45d60f5d4d8"><code>1b7faf0</code></a>
feat: add <code>skipJSXText</code> option to
<code>no-irregular-whitespace</code> rule (<a
href="https://redirect.github.com/eslint/eslint/issues/17182">#17182</a>)
(Azat S)</li>
</ul>
<h2>Bug Fixes</h2>
<ul>
<li><a
href="https://github.com/eslint/eslint/commit/5338b56fda7f47d16bdb23514f1e95b24de7b92f"><code>5338b56</code></a>
fix: normalize <code>cwd</code> passed to
<code>ESLint</code>/<code>FlatESLint</code> constructor (<a
href="https://redirect.github.com/eslint/eslint/issues/17277">#17277</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/54383e69b092ef537d59a1f7799a85b1412f4e59"><code>54383e6</code></a>
fix: Remove <code>no-extra-parens</code> autofix for potential
directives (<a
href="https://redirect.github.com/eslint/eslint/issues/17022">#17022</a>)
(Francesco Trotta)</li>
</ul>
<h2>Documentation</h2>
<ul>
<li><a
href="https://github.com/eslint/eslint/commit/8b855ea058992d5446d1d6dc6394ee683c3200a0"><code>8b855ea</code></a>
docs: resubmit pr17061 doc changes (<a
href="https://redirect.github.com/eslint/eslint/issues/17292">#17292</a>)
(唯然)</li>
<li><a
href="https://github.com/eslint/eslint/commit/372722eac32ca9e3f31cf0d0bc10317c6f153369"><code>372722e</code></a>
docs: resubmit pr17012 doc changes (<a
href="https://redirect.github.com/eslint/eslint/issues/17293">#17293</a>)
(唯然)</li>
<li><a
href="https://github.com/eslint/eslint/commit/67e7af3fdbdb4648b747dfd669be4decfe24086a"><code>67e7af3</code></a>
docs: resubmit custom-rules doc changes (<a
href="https://redirect.github.com/eslint/eslint/issues/17294">#17294</a>)
(唯然)</li>
<li><a
href="https://github.com/eslint/eslint/commit/9e3d77cba65d0e38e07996e57961fb04f30d9303"><code>9e3d77c</code></a>
docs: Resubmit Fix formatting in Custom Rules docs (<a
href="https://redirect.github.com/eslint/eslint/issues/17281">#17281</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/503647a0b94ca8c776d7e7e8c54c8b1d32904467"><code>503647a</code></a>
docs: Resubmit markVariableAsUsed docs (<a
href="https://redirect.github.com/eslint/eslint/issues/17280">#17280</a>)
(Nicholas C. Zakas)</li>
<li><a
href="https://github.com/eslint/eslint/commit/e0cf0d86d985ed2b2f901dd9aab5ccd2fff062ad"><code>e0cf0d8</code></a>
docs: Custom rule &amp; plugin tutorial (<a
href="https://redirect.github.com/eslint/eslint/issues/17024">#17024</a>)
(Ben Perlmutter)</li>
<li><a
href="https://github.com/eslint/eslint/commit/8e51ea943c2fcd05bd8917cfa89e36b91209c7cd"><code>8e51ea9</code></a>
docs: resubmit <code>no-new</code> rule documentation (<a
href="https://redirect.github.com/eslint/eslint/issues/17264">#17264</a>)
(Nitin Kumar)</li>
<li><a
href="https://github.com/eslint/eslint/commit/1b217f8de15961fd3c80389621080132f517a0fb"><code>1b217f8</code></a>
docs: resubmit <code>Custom Processors</code> documentation (<a
href="https://redirect.github.com/eslint/eslint/issues/17265">#17265</a>)
(Nitin Kumar)</li>
<li><a
href="https://github.com/eslint/eslint/commit/428fc76806dea1ac82484d628261a5385f928e6a"><code>428fc76</code></a>
docs: resubmit <code>Create Plugins</code> documentation (<a
href="https://redirect.github.com/eslint/eslint/issues/17268">#17268</a>)
(Nitin Kumar)</li>
<li><a
href="https://github.com/eslint/eslint/commit/bdca88cf4f8b7888cb72197bfe9c1d90b490a0dd"><code>bdca88c</code></a>
docs: resubmit <code>Configuration Files</code> documentation (<a
href="https://redirect.github.com/eslint/eslint/issues/17267">#17267</a>)
(Nitin Kumar)</li>
<li><a
href="https://github.com/eslint/eslint/commit/f5c01f281ad288b1a0ebddbf579230ae11587c6c"><code>f5c01f2</code></a>
docs: resubmit <code>Manage Issues</code> documentation (<a
href="https://redirect.github.com/eslint/eslint/issues/17266">#17266</a>)
(Nitin Kumar)</li>
<li><a
href="https://github.com/eslint/eslint/commit/b1992954591a3f4d8417013f52739b5fef4e0cd7"><code>b199295</code></a>
docs: Resubmit custom rules update docs (<a
href="https://redirect.github.com/eslint/eslint/issues/17273">#17273</a>)
(Ben Perlmutter)</li>
<li><a
href="https://github.com/eslint/eslint/commit/0e9980c3a8a1e554fdb377305c0ebe9e94a354c9"><code>0e9980c</code></a>
docs: add new <code>omitLastInOneLineClassBody</code> option to the
<code>semi</code> rule (<a
href="https://redirect.github.com/eslint/eslint/issues/17263">#17263</a>)
(Nitin Kumar)</li>
<li><a
href="https://github.com/eslint/eslint/commit/cb2560f7a393e74b761faa9adad938fb1deb947d"><code>cb2560f</code></a>
docs: Resubmit getScope/getDeclaredVariables docs (<a
href="https://redirect.github.com/eslint/eslint/issues/17262">#17262</a>)
(Nicholas C. Zakas)</li>
<li><a
href="https://github.com/eslint/eslint/commit/85d2b30bc318c1355e52ebb21c56cca32f0ab198"><code>85d2b30</code></a>
docs: explain how to include predefined globals (<a
href="https://redirect.github.com/eslint/eslint/issues/17261">#17261</a>)
(Marcus Wyatt)</li>
<li><a
href="https://github.com/eslint/eslint/commit/de4d3c14c30a88795b9075d59827d3fe63a42c5e"><code>de4d3c1</code></a>
docs: update flat config default ignore patterns (<a
href="https://redirect.github.com/eslint/eslint/issues/17258">#17258</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/3912f3a225c12bfb5ce9b7ba26c2b5301e6275bd"><code>3912f3a</code></a>
docs: Improve <code>ignores</code> documentation (<a
href="https://redirect.github.com/eslint/eslint/issues/17239">#17239</a>)
(Francesco Trotta)</li>
<li><a
href="https://github.com/eslint/eslint/commit/35e11d3248e00b711fd652836edc900f22af0ebd"><code>35e11d3</code></a>
docs: fix typos and missing info (<a
href="https://redirect.github.com/eslint/eslint/issues/17257">#17257</a>)
(Ed Lucas)</li>
<li><a
href="https://github.com/eslint/eslint/commit/0bc257c290b12fcda85cb61b40d55fc2be0f938c"><code>0bc257c</code></a>
docs: Clarify <code>no-div-regex</code> rule docs (<a
href="https://redirect.github.com/eslint/eslint/issues/17051">#17051</a>)
(<a
href="https://redirect.github.com/eslint/eslint/issues/17255">#17255</a>)
(Francesco Trotta)</li>
<li><a
href="https://github.com/eslint/eslint/commit/788d83629a3790a7db6f52dcf0b4bddf51c6d063"><code>788d836</code></a>
docs: add references to MIT License (<a
href="https://redirect.github.com/eslint/eslint/issues/17248">#17248</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/58aab6b6c09996875418aefeeb0fd76c50caef7a"><code>58aab6b</code></a>
docs: Update README (GitHub Actions Bot)</li>
<li><a
href="https://github.com/eslint/eslint/commit/3ef58140550cf8ff34af35fc4d9a1f9a124fe0e6"><code>3ef5814</code></a>
docs: Revert all changes after the license change (<a
href="https://redirect.github.com/eslint/eslint/issues/17227">#17227</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/03fc4aa847bd0445e7b3ea81bcc9523b1847facc"><code>03fc4aa</code></a>
docs: Update README (GitHub Actions Bot)</li>
</ul>
<h2>Chores</h2>
<ul>
<li><a
href="https://github.com/eslint/eslint/commit/78350f63045c82b7990bb7bfe5080c5ad5e1c3f5"><code>78350f6</code></a>
chore: upgrade <code>@​eslint/js</code><a
href="https://github.com/8"><code>@​8</code></a>.43.0 (<a
href="https://redirect.github.com/eslint/eslint/issues/17295">#17295</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/62bf759124811b013ad7906c2536deb8b39c31a8"><code>62bf759</code></a>
chore: package.json update for <code>@​eslint/js</code> release (ESLint
Jenkins)</li>
<li><a
href="https://github.com/eslint/eslint/commit/e0a2448e0c0ef354e69998858846630a3fce8ebe"><code>e0a2448</code></a>
chore: docs package.license ISC =&gt; MIT (<a
href="https://redirect.github.com/eslint/eslint/issues/17254">#17254</a>)
(唯然)</li>
<li><a
href="https://github.com/eslint/eslint/commit/6a0196c51310630a0ff96a1e8d7f257c2c7adda9"><code>6a0196c</code></a>
chore: use eslint-plugin-eslint-plugin flat configs (<a
href="https://redirect.github.com/eslint/eslint/issues/17204">#17204</a>)
(Milos Djermanovic)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/eslint/eslint/blob/main/CHANGELOG.md">eslint's
changelog</a>.</em></p>
<blockquote>
<p>v8.43.0 - June 16, 2023</p>
<ul>
<li><a
href="https://github.com/eslint/eslint/commit/78350f63045c82b7990bb7bfe5080c5ad5e1c3f5"><code>78350f6</code></a>
chore: upgrade <code>@​eslint/js</code><a
href="https://github.com/8"><code>@​8</code></a>.43.0 (<a
href="https://redirect.github.com/eslint/eslint/issues/17295">#17295</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/8b855ea058992d5446d1d6dc6394ee683c3200a0"><code>8b855ea</code></a>
docs: resubmit pr17061 doc changes (<a
href="https://redirect.github.com/eslint/eslint/issues/17292">#17292</a>)
(唯然)</li>
<li><a
href="https://github.com/eslint/eslint/commit/62bf759124811b013ad7906c2536deb8b39c31a8"><code>62bf759</code></a>
chore: package.json update for <code>@​eslint/js</code> release (ESLint
Jenkins)</li>
<li><a
href="https://github.com/eslint/eslint/commit/14581ff15aaee5a55c46bbf4983818ddc8dd7cb1"><code>14581ff</code></a>
feat: directive prologue detection and autofix condition in
<code>quotes</code> (<a
href="https://redirect.github.com/eslint/eslint/issues/17284">#17284</a>)
(Francesco Trotta)</li>
<li><a
href="https://github.com/eslint/eslint/commit/372722eac32ca9e3f31cf0d0bc10317c6f153369"><code>372722e</code></a>
docs: resubmit pr17012 doc changes (<a
href="https://redirect.github.com/eslint/eslint/issues/17293">#17293</a>)
(唯然)</li>
<li><a
href="https://github.com/eslint/eslint/commit/67e7af3fdbdb4648b747dfd669be4decfe24086a"><code>67e7af3</code></a>
docs: resubmit custom-rules doc changes (<a
href="https://redirect.github.com/eslint/eslint/issues/17294">#17294</a>)
(唯然)</li>
<li><a
href="https://github.com/eslint/eslint/commit/5338b56fda7f47d16bdb23514f1e95b24de7b92f"><code>5338b56</code></a>
fix: normalize <code>cwd</code> passed to
<code>ESLint</code>/<code>FlatESLint</code> constructor (<a
href="https://redirect.github.com/eslint/eslint/issues/17277">#17277</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/9e3d77cba65d0e38e07996e57961fb04f30d9303"><code>9e3d77c</code></a>
docs: Resubmit Fix formatting in Custom Rules docs (<a
href="https://redirect.github.com/eslint/eslint/issues/17281">#17281</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/503647a0b94ca8c776d7e7e8c54c8b1d32904467"><code>503647a</code></a>
docs: Resubmit markVariableAsUsed docs (<a
href="https://redirect.github.com/eslint/eslint/issues/17280">#17280</a>)
(Nicholas C. Zakas)</li>
<li><a
href="https://github.com/eslint/eslint/commit/54383e69b092ef537d59a1f7799a85b1412f4e59"><code>54383e6</code></a>
fix: Remove <code>no-extra-parens</code> autofix for potential
directives (<a
href="https://redirect.github.com/eslint/eslint/issues/17022">#17022</a>)
(Francesco Trotta)</li>
<li><a
href="https://github.com/eslint/eslint/commit/e0cf0d86d985ed2b2f901dd9aab5ccd2fff062ad"><code>e0cf0d8</code></a>
docs: Custom rule &amp; plugin tutorial (<a
href="https://redirect.github.com/eslint/eslint/issues/17024">#17024</a>)
(Ben Perlmutter)</li>
<li><a
href="https://github.com/eslint/eslint/commit/8e51ea943c2fcd05bd8917cfa89e36b91209c7cd"><code>8e51ea9</code></a>
docs: resubmit <code>no-new</code> rule documentation (<a
href="https://redirect.github.com/eslint/eslint/issues/17264">#17264</a>)
(Nitin Kumar)</li>
<li><a
href="https://github.com/eslint/eslint/commit/1b217f8de15961fd3c80389621080132f517a0fb"><code>1b217f8</code></a>
docs: resubmit <code>Custom Processors</code> documentation (<a
href="https://redirect.github.com/eslint/eslint/issues/17265">#17265</a>)
(Nitin Kumar)</li>
<li><a
href="https://github.com/eslint/eslint/commit/428fc76806dea1ac82484d628261a5385f928e6a"><code>428fc76</code></a>
docs: resubmit <code>Create Plugins</code> documentation (<a
href="https://redirect.github.com/eslint/eslint/issues/17268">#17268</a>)
(Nitin Kumar)</li>
<li><a
href="https://github.com/eslint/eslint/commit/bdca88cf4f8b7888cb72197bfe9c1d90b490a0dd"><code>bdca88c</code></a>
docs: resubmit <code>Configuration Files</code> documentation (<a
href="https://redirect.github.com/eslint/eslint/issues/17267">#17267</a>)
(Nitin Kumar)</li>
<li><a
href="https://github.com/eslint/eslint/commit/f5c01f281ad288b1a0ebddbf579230ae11587c6c"><code>f5c01f2</code></a>
docs: resubmit <code>Manage Issues</code> documentation (<a
href="https://redirect.github.com/eslint/eslint/issues/17266">#17266</a>)
(Nitin Kumar)</li>
<li><a
href="https://github.com/eslint/eslint/commit/b1992954591a3f4d8417013f52739b5fef4e0cd7"><code>b199295</code></a>
docs: Resubmit custom rules update docs (<a
href="https://redirect.github.com/eslint/eslint/issues/17273">#17273</a>)
(Ben Perlmutter)</li>
<li><a
href="https://github.com/eslint/eslint/commit/e50fac3f8f998f729e3080e256066db3a7827c67"><code>e50fac3</code></a>
feat: add declaration loc to message in block-scoped-var (<a
href="https://redirect.github.com/eslint/eslint/issues/17252">#17252</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/0e9980c3a8a1e554fdb377305c0ebe9e94a354c9"><code>0e9980c</code></a>
docs: add new <code>omitLastInOneLineClassBody</code> option to the
<code>semi</code> rule (<a
href="https://redirect.github.com/eslint/eslint/issues/17263">#17263</a>)
(Nitin Kumar)</li>
<li><a
href="https://github.com/eslint/eslint/commit/cb2560f7a393e74b761faa9adad938fb1deb947d"><code>cb2560f</code></a>
docs: Resubmit getScope/getDeclaredVariables docs (<a
href="https://redirect.github.com/eslint/eslint/issues/17262">#17262</a>)
(Nicholas C. Zakas)</li>
<li><a
href="https://github.com/eslint/eslint/commit/85d2b30bc318c1355e52ebb21c56cca32f0ab198"><code>85d2b30</code></a>
docs: explain how to include predefined globals (<a
href="https://redirect.github.com/eslint/eslint/issues/17261">#17261</a>)
(Marcus Wyatt)</li>
<li><a
href="https://github.com/eslint/eslint/commit/de4d3c14c30a88795b9075d59827d3fe63a42c5e"><code>de4d3c1</code></a>
docs: update flat config default ignore patterns (<a
href="https://redirect.github.com/eslint/eslint/issues/17258">#17258</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/3912f3a225c12bfb5ce9b7ba26c2b5301e6275bd"><code>3912f3a</code></a>
docs: Improve <code>ignores</code> documentation (<a
href="https://redirect.github.com/eslint/eslint/issues/17239">#17239</a>)
(Francesco Trotta)</li>
<li><a
href="https://github.com/eslint/eslint/commit/35e11d3248e00b711fd652836edc900f22af0ebd"><code>35e11d3</code></a>
docs: fix typos and missing info (<a
href="https://redirect.github.com/eslint/eslint/issues/17257">#17257</a>)
(Ed Lucas)</li>
<li><a
href="https://github.com/eslint/eslint/commit/e0a2448e0c0ef354e69998858846630a3fce8ebe"><code>e0a2448</code></a>
chore: docs package.license ISC =&gt; MIT (<a
href="https://redirect.github.com/eslint/eslint/issues/17254">#17254</a>)
(唯然)</li>
<li><a
href="https://github.com/eslint/eslint/commit/0bc257c290b12fcda85cb61b40d55fc2be0f938c"><code>0bc257c</code></a>
docs: Clarify <code>no-div-regex</code> rule docs (<a
href="https://redirect.github.com/eslint/eslint/issues/17051">#17051</a>)
(<a
href="https://redirect.github.com/eslint/eslint/issues/17255">#17255</a>)
(Francesco Trotta)</li>
<li><a
href="https://github.com/eslint/eslint/commit/1b7faf0702b1af86b6a0ddafc37cf45d60f5d4d8"><code>1b7faf0</code></a>
feat: add <code>skipJSXText</code> option to
<code>no-irregular-whitespace</code> rule (<a
href="https://redirect.github.com/eslint/eslint/issues/17182">#17182</a>)
(Azat S)</li>
<li><a
href="https://github.com/eslint/eslint/commit/788d83629a3790a7db6f52dcf0b4bddf51c6d063"><code>788d836</code></a>
docs: add references to MIT License (<a
href="https://redirect.github.com/eslint/eslint/issues/17248">#17248</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/58aab6b6c09996875418aefeeb0fd76c50caef7a"><code>58aab6b</code></a>
docs: Update README (GitHub Actions Bot)</li>
<li><a
href="https://github.com/eslint/eslint/commit/6a0196c51310630a0ff96a1e8d7f257c2c7adda9"><code>6a0196c</code></a>
chore: use eslint-plugin-eslint-plugin flat configs (<a
href="https://redirect.github.com/eslint/eslint/issues/17204">#17204</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/030a82737f51563f9a7b4985fc91b6d8eab54fce"><code>030a827</code></a>
Revert &quot;feat: docs license (<a
href="https://redirect.github.com/eslint/eslint/issues/17010">#17010</a>)&quot;
(<a
href="https://redirect.github.com/eslint/eslint/issues/17231">#17231</a>)
(唯然)</li>
<li><a
href="https://github.com/eslint/eslint/commit/3ef58140550cf8ff34af35fc4d9a1f9a124fe0e6"><code>3ef5814</code></a>
docs: Revert all changes after the license change (<a
href="https://redirect.github.com/eslint/eslint/issues/17227">#17227</a>)
(Milos Djermanovic)</li>
<li><a
href="https://github.com/eslint/eslint/commit/03fc4aa847bd0445e7b3ea81bcc9523b1847facc"><code>03fc4aa</code></a>
docs: Update README (GitHub Actions Bot)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/eslint/eslint/commit/150a74b29fae11af344ebbd29f24b5c1110f5848"><code>150a74b</code></a>
8.43.0</li>
<li><a
href="https://github.com/eslint/eslint/commit/69a628033a016176b44bb61f54cb3d9e762048e1"><code>69a6280</code></a>
Build: changelog update for 8.43.0</li>
<li><a
href="https://github.com/eslint/eslint/commit/78350f63045c82b7990bb7bfe5080c5ad5e1c3f5"><code>78350f6</code></a>
chore: upgrade <code>@​eslint/js</code><a
href="https://github.com/8"><code>@​8</code></a>.43.0 (<a
href="https://redirect.github.com/eslint/eslint/issues/17295">#17295</a>)</li>
<li><a
href="https://github.com/eslint/eslint/commit/8b855ea058992d5446d1d6dc6394ee683c3200a0"><code>8b855ea</code></a>
docs: resubmit pr17061 doc changes (<a
href="https://redirect.github.com/eslint/eslint/issues/17292">#17292</a>)</li>
<li><a
href="https://github.com/eslint/eslint/commit/62bf759124811b013ad7906c2536deb8b39c31a8"><code>62bf759</code></a>
chore: package.json update for <code>@​eslint/js</code> release</li>
<li><a
href="https://github.com/eslint/eslint/commit/14581ff15aaee5a55c46bbf4983818ddc8dd7cb1"><code>14581ff</code></a>
feat: directive prologue detection and autofix condition in
<code>quotes</code> (<a
href="https://redirect.github.com/eslint/eslint/issues/17284">#17284</a>)</li>
<li><a
href="https://github.com/eslint/eslint/commit/372722eac32ca9e3f31cf0d0bc10317c6f153369"><code>372722e</code></a>
docs: resubmit pr17012 doc changes (<a
href="https://redirect.github.com/eslint/eslint/issues/17293">#17293</a>)</li>
<li><a
href="https://github.com/eslint/eslint/commit/67e7af3fdbdb4648b747dfd669be4decfe24086a"><code>67e7af3</code></a>
docs: resubmit custom-rules doc changes (<a
href="https://redirect.github.com/eslint/eslint/issues/17294">#17294</a>)</li>
<li><a
href="https://github.com/eslint/eslint/commit/5338b56fda7f47d16bdb23514f1e95b24de7b92f"><code>5338b56</code></a>
fix: normalize <code>cwd</code> passed to
<code>ESLint</code>/<code>FlatESLint</code> constructor (<a
href="https://redirect.github.com/eslint/eslint/issues/17277">#17277</a>)</li>
<li><a
href="https://github.com/eslint/eslint/commit/9e3d77cba65d0e38e07996e57961fb04f30d9303"><code>9e3d77c</code></a>
docs: Resubmit Fix formatting in Custom Rules docs (<a
href="https://redirect.github.com/eslint/eslint/issues/17281">#17281</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/eslint/eslint/compare/v8.42.0...v8.43.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=eslint&package-manager=npm_and_yarn&previous-version=8.42.0&new-version=8.43.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Shawn Callegari <[email protected]>
 2023-06-25 22:34:35 +00:00
dependabot[bot] a81884e946 Bump @typescript-eslint/parser from 5.59.11 to 5.60.0 in /samples/apps (#1698) 
Bumps
[@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser)
from 5.59.11 to 5.60.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/typescript-eslint/typescript-eslint/releases"><code>@​typescript-eslint/parser</code>'s
releases</a>.</em></p>
<blockquote>
<h2>v5.60.0</h2>
<h1><a
href="https://github.com/typescript-eslint/typescript-eslint/compare/v5.59.11...v5.60.0">5.60.0</a>
(2023-06-19)</h1>
<h3>Features</h3>
<ul>
<li><strong>eslint-plugin:</strong> [restrict-plus-operands] add allow*
options (<a
href="https://redirect.github.com/typescript-eslint/typescript-eslint/issues/6161">#6161</a>)
(<a
href="https://github.com/typescript-eslint/typescript-eslint/commit/def09f88cdb4a85cebb8619b45931f7e2c88dfc0">def09f8</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md"><code>@​typescript-eslint/parser</code>'s
changelog</a>.</em></p>
<blockquote>
<h1><a
href="https://github.com/typescript-eslint/typescript-eslint/compare/v5.59.11...v5.60.0">5.60.0</a>
(2023-06-19)</h1>
<p><strong>Note:</strong> Version bump only for package
<code>@​typescript-eslint/parser</code></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/typescript-eslint/typescript-eslint/commit/c09b1c0252cbbf58e94ca5d671b6e05f29511144"><code>c09b1c0</code></a>
chore: publish v5.60.0</li>
<li>See full diff in <a
href="https://github.com/typescript-eslint/typescript-eslint/commits/v5.60.0/packages/parser">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@typescript-eslint/parser&package-manager=npm_and_yarn&previous-version=5.59.11&new-version=5.60.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
 2023-06-25 22:27:50 +00:00
Shawn Callegari a46ac54bdd Update dependabot.yml to weekly updates 2023-06-25 15:26:55 -07:00
Shawn Callegari 3c4e82c6ad Update EMBEDDINGS.md 
Remove broken external link, blocking all PRs.
 2023-06-25 15:24:24 -07:00
dependabot[bot] adef41c18d Bump pytest from 7.3.2 to 7.4.0 in /python (#1700) 
Bumps [pytest](https://github.com/pytest-dev/pytest) from 7.3.2 to
7.4.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pytest-dev/pytest/releases">pytest's
releases</a>.</em></p>
<blockquote>
<h2>7.4.0</h2>
<h1>pytest 7.4.0 (2023-06-23)</h1>
<h2>Features</h2>
<ul>
<li><a
href="https://redirect.github.com/pytest-dev/pytest/issues/10901">#10901</a>:
Added <code>ExceptionInfo.from_exception()
&lt;pytest.ExceptionInfo.from_exception&gt;</code>{.interpreted-text
role=&quot;func&quot;}, a simpler way to create an
<code>~pytest.ExceptionInfo</code>{.interpreted-text
role=&quot;class&quot;} from an exception.
This can replace <code>ExceptionInfo.from_exc_info()
&lt;pytest.ExceptionInfo.from_exc_info()&gt;</code>{.interpreted-text
role=&quot;func&quot;} for most uses.</li>
</ul>
<h2>Improvements</h2>
<ul>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/10872">#10872</a>:
Update test log report annotation to named tuple and fixed inconsistency
in docs for <code>pytest_report_teststatus</code>{.interpreted-text
role=&quot;hook&quot;} hook.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/10907">#10907</a>:
When an exception traceback to be displayed is completely filtered out
(by mechanisms such as <code>__tracebackhide__</code>, internal frames,
and similar), now only the exception string and the following message
are shown:</p>
<p>&quot;All traceback entries are hidden. Pass
[--full-trace]{.title-ref} to see hidden and internal frames.&quot;.</p>
<p>Previously, the last frame of the traceback was shown, even though it
was hidden.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/10940">#10940</a>:
Improved verbose output (<code>-vv</code>) of <code>skip</code> and
<code>xfail</code> reasons by performing text wrapping while leaving a
clear margin for progress output.</p>
<p>Added <code>TerminalReporter.wrap_write()</code> as a helper for
that.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/10991">#10991</a>:
Added handling of <code>%f</code> directive to print microseconds in log
format options, such as <code>log-date-format</code>.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11005">#11005</a>:
Added the underlying exception to the cache provider's path creation and
write warning messages.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11013">#11013</a>:
Added warning when <code>testpaths</code>{.interpreted-text
role=&quot;confval&quot;} is set, but paths are not found by glob. In
this case, pytest will fall back to searching from the current
directory.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11043">#11043</a>:
When [--confcutdir]{.title-ref} is not specified, and there is no config
file present, the conftest cutoff directory ([--confcutdir]{.title-ref})
is now set to the <code>rootdir &lt;rootdir&gt;</code>{.interpreted-text
role=&quot;ref&quot;}.
Previously in such cases, [conftest.py]{.title-ref} files would be
probed all the way to the root directory of the filesystem.
If you are badly affected by this change, consider adding an empty
config file to your desired cutoff directory, or explicitly set
[--confcutdir]{.title-ref}.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11081">#11081</a>:
The <code>norecursedirs</code>{.interpreted-text
role=&quot;confval&quot;} check is now performed in a
<code>pytest_ignore_collect</code>{.interpreted-text
role=&quot;hook&quot;} implementation, so plugins can affect it.</p>
<p>If after updating to this version you see that your
[norecursedirs]{.title-ref} setting is not being respected,
it means that a conftest or a plugin you use has a bad
[pytest_ignore_collect]{.title-ref} implementation.
Most likely, your hook returns [False]{.title-ref} for paths it does not
want to ignore,
which ends the processing and doesn't allow other plugins, including
pytest itself, to ignore the path.
The fix is to return [None]{.title-ref} instead of [False]{.title-ref}
for paths your hook doesn't want to ignore.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/8711">#8711</a>:
<code>caplog.set_level()
&lt;pytest.LogCaptureFixture.set_level&gt;</code>{.interpreted-text
role=&quot;func&quot;} and <code>caplog.at_level()
&lt;pytest.LogCaptureFixture.at_level&gt;</code>{.interpreted-text
role=&quot;func&quot;}
will temporarily enable the requested <code>level</code> if
<code>level</code> was disabled globally via
<code>logging.disable(LEVEL)</code>.</p>
</li>
</ul>
<h2>Bug Fixes</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/pytest-dev/pytest/commit/d9bf9dbec104af1e3a2c02b04f4e1d501d5d86a2"><code>d9bf9db</code></a>
Prepare release version 7.4.0</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/64319dbc01767c73161be630bb6986c4f1402c3e"><code>64319db</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/11128">#11128</a>
from bluetech/pythonpath-note</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/1e8135df16fff350d0097a41b739745a9e14edec"><code>1e8135d</code></a>
reference: add note that <code>pythonpath</code> does not affect
<code>-p</code></li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/1e32a4b57030d06eec09e6c1d484e55709f59991"><code>1e32a4b</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/10935">#10935</a>
from nondescryptid/10328</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/faa1f9d2ad88d788cf035e5ed8ed78d248c24c09"><code>faa1f9d</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/11125">#11125</a>
from bluetech/initial-conftests-testpaths</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/14890329dcdc37085a8ac9c53ce332df9faead30"><code>1489032</code></a>
config: fix the paths considered for initial conftest discovery</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/d97d44a97af2303eb3f3aea1f16fd834f5415509"><code>d97d44a</code></a>
config: extract initial paths/nodeids args logic to a function</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/f6b995e9d59a0b7e1e52fb64185e9e1d1dae367d"><code>f6b995e</code></a>
Use utf-8 debug file</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/661b938fcad0ece7d017d76d412fff220e43a865"><code>661b938</code></a>
Add encoding in more tests</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/7e510769b4a9b67ef3802a894b36e7978fa222f8"><code>7e51076</code></a>
Encoding for subprocess.run</li>
<li>Additional commits viewable in <a
href="https://github.com/pytest-dev/pytest/compare/7.3.2...7.4.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pytest&package-manager=pip&previous-version=7.3.2&new-version=7.4.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
 2023-06-25 22:03:08 +00:00
dependabot[bot] e3d3541471 Bump ipykernel from 6.23.2 to 6.23.3 in /python (#1701) 
Bumps [ipykernel](https://github.com/ipython/ipykernel) from 6.23.2 to
6.23.3.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/ipython/ipykernel/releases">ipykernel's
releases</a>.</em></p>
<blockquote>
<h2>v6.23.3</h2>
<h2>6.23.3</h2>
<p>(<a
href="https://github.com/ipython/ipykernel/compare/v6.23.2...ea3e6479aca70f87282ec0b60412f2cfba59eb35">Full
Changelog</a>)</p>
<h3>Bugs fixed</h3>
<ul>
<li>Check existence of connection_file before writing <a
href="https://redirect.github.com/ipython/ipykernel/pull/1127">#1127</a>
(<a href="https://github.com/fecet"><code>@​fecet</code></a>)</li>
</ul>
<h3>Contributors to this release</h3>
<p>(<a
href="https://github.com/ipython/ipykernel/graphs/contributors?from=2023-06-12&amp;to=2023-06-23&amp;type=c">GitHub
contributors page for this release</a>)</p>
<p><a
href="https://github.com/search?q=repo%3Aipython%2Fipykernel+involves%3Ablink1073+updated%3A2023-06-12..2023-06-23&amp;type=Issues"><code>@​blink1073</code></a>
| <a
href="https://github.com/search?q=repo%3Aipython%2Fipykernel+involves%3Afecet+updated%3A2023-06-12..2023-06-23&amp;type=Issues"><code>@​fecet</code></a></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/ipython/ipykernel/blob/main/CHANGELOG.md">ipykernel's
changelog</a>.</em></p>
<blockquote>
<h2>6.23.3</h2>
<p>(<a
href="https://github.com/ipython/ipykernel/compare/v6.23.2...ea3e6479aca70f87282ec0b60412f2cfba59eb35">Full
Changelog</a>)</p>
<h3>Bugs fixed</h3>
<ul>
<li>Check existence of connection_file before writing <a
href="https://redirect.github.com/ipython/ipykernel/pull/1127">#1127</a>
(<a href="https://github.com/fecet"><code>@​fecet</code></a>)</li>
</ul>
<h3>Contributors to this release</h3>
<p>(<a
href="https://github.com/ipython/ipykernel/graphs/contributors?from=2023-06-12&amp;to=2023-06-23&amp;type=c">GitHub
contributors page for this release</a>)</p>
<p><a
href="https://github.com/search?q=repo%3Aipython%2Fipykernel+involves%3Ablink1073+updated%3A2023-06-12..2023-06-23&amp;type=Issues"><code>@​blink1073</code></a>
| <a
href="https://github.com/search?q=repo%3Aipython%2Fipykernel+involves%3Afecet+updated%3A2023-06-12..2023-06-23&amp;type=Issues"><code>@​fecet</code></a></p>
<!-- raw HTML omitted -->
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/ipython/ipykernel/commit/99b2ec4f4e29e214128b860cb9678e9bd275d959"><code>99b2ec4</code></a>
Publish 6.23.3</li>
<li><a
href="https://github.com/ipython/ipykernel/commit/ea3e6479aca70f87282ec0b60412f2cfba59eb35"><code>ea3e647</code></a>
fix: check existence of connection_file before writing (<a
href="https://redirect.github.com/ipython/ipykernel/issues/1127">#1127</a>)</li>
<li>See full diff in <a
href="https://github.com/ipython/ipykernel/compare/v6.23.2...v6.23.3">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=ipykernel&package-manager=pip&previous-version=6.23.2&new-version=6.23.3)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
 2023-06-25 22:02:19 +00:00
Desmond HowardandShawn Callegari 71120b20fb Fix ESLint in samples/apps (#1452) 
### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->
correctly using ESLint in our sample apps will help us
- follow best practices, 
- cut down on bugs that the linter can catch, and
- enforce a unified style

### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->
- adds `.env.local` to each app to disable ESLint in all environments
  - temporary until the violations are fixed in the app
- this seemed to be the easiest way to disable ESLint without folks
having to do anything, open to suggestions here.
- this is needed because now the build picks up on our config file and
will fail since there are currently violations
- adds a `package.json` to `samples/apps` for the shared dependencies
needed for running `eslint`
- adds the `npm run lint` script and `eslint` package to apps where not
already present
- removes unneeded ESLint config/dependencies from CopilotChat
- renames `.eslingrc.js` to `.eslintrc.js`

### Note
**this doesn't start enforcing ESLint anywhere or fix any violations**,
and rather just fixes the config so that we can begin to correct the
errors.

there are quite a number of violations just in CopilotChat alone:

![image](https://github.com/microsoft/semantic-kernel/assets/52973358/0ac17df8-35a8-4c31-929a-0a9629d5d031)

`eslint --fix` can fix about half of these, albeit we should review
these changes carefully if used.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->
- [X] The code builds clean without any errors or warnings
- [X] The PR follows SK Contribution Guidelines
(https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
- [X] The code follows the .NET coding conventions
(https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions)
verified with `dotnet format`
- [X] All unit tests pass, and I have added new tests where possible
- [X] I didn't break anyone 😄

---------

Co-authored-by: Shawn Callegari <[email protected]>
 2023-06-23 17:28:24 +00:00
dependabot[bot] b3f74f6623 Bump NRedisStack from 0.6.1 to 0.7.0 in /dotnet (#1509) 
Bumps NRedisStack from 0.6.1 to 0.7.0.


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=NRedisStack&package-manager=nuget&previous-version=0.6.1&new-version=0.7.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
 2023-06-23 16:31:11 +00:00