-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump log4j-core from 2.16.0 to 2.17.0 in /sdk/cosmos/azure-cosmos-benchmark #26104
Bump log4j-core from 2.16.0 to 2.17.0 in /sdk/cosmos/azure-cosmos-benchmark #26104
Conversation
Bumps log4j-core from 2.16.0 to 2.17.0. --- updated-dependencies: - dependency-name: org.apache.logging.log4j:log4j-core dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Thank you for your contribution dependabot[bot]! We will review the pull request and get back to you soon. |
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
/check-enforcer override |
Release machinelearningservices microsoft.machine learning services 2023 10 01 shadow (Azure#26104) * Adds base for updating Microsoft.MachineLearningServices from version stable/2023-04-01 to version 2023-10-01 * fix rebase * Updates API version in new specs and examples * mfe.json update description to fix linting errors (Azure#24968) Co-authored-by: Kayla Ames <kaseager@microsoft.com> * add headers for start/stop/restart compute examples (Azure#25072) * Adding SubscriptionId and ResourceGroup for Azure Datastore (Azure#25289) * Add query param in list job api (Azure#25374) Co-authored-by: Shail Paragbhai Shah <shaisha@microsoft.com> * [MachineLearning]Try fixing some lint error in 10-01 version (Azure#25519) * Try fixing some lint error * bug fix * remove unused definition * Update Example * adding queue settings to Oct 2023 stable api version (Azure#25765) * adding queue settings to Oct 2023 stable api version * update new line --------- Co-authored-by: Aaheli Chattopadhyay <aahelic@microsoft.com> * remove job priority (Azure#25775) Co-authored-by: Aaheli Chattopadhyay <aahelic@microsoft.com> * Adding MachineLearningService workspace resource publish API and registry datareference API (Azure#25619) * Adding machinelearningservices workspace publish and registry datareference API * minimize diff * minor updates on put job api summary * remove two unneeded APIs * remove extra adding long running annotation * Add managed Vnet to stable version (Azure#25729) * Add managed Vnet to stable version * update missing parameter * Update missing ref * meaningless commit trigger pipeline again * Revert "meaningless commit trigger pipeline again" This reverts commit baa386b8cf0abb96b461a27d9060188e7ed0581e. * add missing ref * Update example version * trigger pipeline * Revert "trigger pipeline" This reverts commit f989c4c91ca85dde28fa636ed82ba9c742a05db9. * add force to purge parameter * trigger pipeline * Revert "trigger pipeline" This reverts commit 42ea0f8c2dc17e42757112b279fae42a4dc6e557. * Update examples * Add format and update examples * [Model Monitoring][GA] - Add model monitoring scenarios (Azure#25801) * Add model monitoring scenarios * add * add * Update mfe.json * Update mfe.json * Update mfe.json * Update mfe.json * add ws vnet properties (Azure#25882) Co-authored-by: Aaheli Chattopadhyay <aahelic@microsoft.com> * Fix circular reference 2023-10-01 (Azure#25879) * TriggerType->ComputeTriggerType * RecurrenceFrequency->ComputeRecurrenceFrequency * RecurrenceSchedule->ComputeRecurrenceSchedule * description --------- Co-authored-by: Kayla Ames <kaseager@microsoft.com> * Adding proxy resource (Azure#25904) Co-authored-by: Shail Paragbhai Shah <shaisha@microsoft.com> * Add feature store api's to GA version (Azure#25594) * Add examples * Adding feature store GA api's * Sync examples * Add examples * Converting to ProxyResource --------- Co-authored-by: Shail Paragbhai Shah <shaisha@microsoft.com> * add serverless compute settings (Azure#26012) Co-authored-by: Aaheli Chattopadhyay <aahelic@microsoft.com> * [MachineLearningService]Add featurestore property to stable version (Azure#26121) * Add workspace kind and featureStoreSettings * add description * Add description for ComputeRuntimeDti * remove featurestore settings for lint * remove Kind * Revert "remove featurestore settings for lint" This reverts commit f4d7ae352baf966aeba9085bd06df3456bd17bef. * Update readme fix --------- Co-authored-by: Kayla Ames <kaseager@microsoft.com> Co-authored-by: libc16 <88697960+libc16@users.noreply.github.com> Co-authored-by: Chunyu Li <79233053+ChunyuMSFT@users.noreply.github.com> Co-authored-by: shail2208 <59747407+shail2208@users.noreply.github.com> Co-authored-by: Shail Paragbhai Shah <shaisha@microsoft.com> Co-authored-by: ZhidaLiu <zhili@microsoft.com> Co-authored-by: ac923 <aahelic@yahoo.com> Co-authored-by: Aaheli Chattopadhyay <aahelic@microsoft.com> Co-authored-by: chaoyu-msft <93601904+chaoyu-msft@users.noreply.github.com> Co-authored-by: Mathieu St-Louis <81435026+mastloui-msft@users.noreply.github.com>
Bumps log4j-core from 2.16.0 to 2.17.0.
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 commands and options
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)@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and languageYou can disable automated security fix PRs for this repo from the Security Alerts page.