Add warning if there are several instances of styled-components on the page

Closes #1011 and also a follow-up to https://github.com/styled-components/styled-components/issues/1395#issuecomment-355268773
I think that even if the https://github.com/styled-components/styled-components/issues/1102 will allow users to solve major issues with having several instances of s-c on the page, there is still a factor of having several modules loaded to the client for no good reason as almost all cases described in several tickets related to this issue (https://github.com/styled-components/styled-components/issues/992, https://github.com/styled-components/styled-components/issues/987) could be solved with just one instance of s-c on the page.
If you feel that this warning is too demanding of the end users of the library, feel free to close the PR (and the issue then should be also closed, probably)

As the StyleSheet.target support (https://github.com/styled-components/styled-components/pull/1491) is finally in the master 🎉  I wanted to discuss the fate of this PR.
The issue of having several instances of styled-components on one page is solvable right now, although as I understand the main purpose of having target is not exactly to bundle several styled-components modules in your app 😉 and detecting the problem would still be not that easy in some cases.
So what should we do with this? Discard this change? Update detection logic to focus more on using the same target on one page, and not just several instances? Leave it as is? Any other ideas?
Just want to know what do you think about this!
/cc @mxstbr @kitten (nice new username, btw 😄) @probablyup

@gribnoysup As target is the "output" of our style tags, the "input" i.e. SSR rehydration is still problematic when two styled-components instances are present 😢 So this is still relevant
cc @mxstbr ready to go I'd say

Thanks for pushing this through @gribnoysup! :tada:


Supply mcsdir as function argument to InitLabels()

Fixes https://github.com/coreos/rkt/issues/3043

LGTM but deferring to @mjg59 for a closer look

LGTM


Add support for Druk Text Wide Web

Change the sidebar font from H6 to Label/L.

Change the sort by drop down text from H6 to Label/L.

Update all the fonts from H1-H6 to using Druk Text Wide Web font face while maintaining the same font size, in theory, it shouldn't break anything.

@lingzizheng Do you have the Durk font files? I would I add it in this folder: https://github.com/reservoirprotocol/sample-marketplace/tree/main/public/fonts

@diegoramosxyz So far we don't plan to fork unless we really need to so let's include keep this on sample marketplace repo.

Druk Text Wide Web Medium Regular.zip

They only use the medium regular for this font

[ ] Custom texts should only be applied to headings (H1-H6) all other styles should remain as inter.

[ ] Collection stats should be Headings/Subtitle style not h6 (see designs)

Ready for staging


Dict fix

Thanks!
I see 5 commits for a single character and it sparks the rebase vs merge debate, but I'll leave that for another PR.
https://www.atlassian.com/git/tutorials/merging-vs-rebasing/workflow-walkthrough


Fix description on PyPI

The markdown description at https://pypi.org/project/pdftotext/ isn't rendered right. Maybe my tools were out of date last time I uploaded. The minimum versions are

setuptools >= 38.6.0
wheel >= 0.31.0
twine >= 1.11.0

Fixed in v2.1.2


User page

// clone khan academy homepage
side bar

Progress
Show Course list
Certificates
Edit profile button

main

Resume my Courses

show xp (xp increases after every video ( like khan academy and codedamn ))

contact us

cc

@SoulNinja-dev Hey can I work on the side bar ?

Hey @SoulNinja-dev, I'd like to develop these components. I've used Material UI to develop many responsive sidebars. I can write vanilla CSS as well.

@praveenscience is handling frontend.


[Feature Request] Tag support for Movies in collections to be excluded

Is your feature request related to a problem? Please describe.
You can't currently exclude movies based on a collection tag for a collection they are in such as PMM tags all collections made with PMM [...]
Describe the solution you'd like
Allow movies in a collection defined by tag to be excluded from deletion rules
Describe alternatives you've considered
As above

I can't seem to be able to get tags of a collection. Instead, I'm able to access labels. Are you referring to labels?


const type parameters get removed

Describe the bug
dprint removes const type parameters intorduced in version 5.0
dprint-plugin-typescript version: 0.84.0
Playground link
Input Code
export const fn = <const Data extends ReadonlyArray<unknown>>(payload: Data) => payload

Expected Output
export const fn = <const Data extends ReadonlyArray<unknown>>(payload: Data) =>
  payload;

Actual Output
export const fn = <Data extends ReadonlyArray<unknown>>(payload: Data) =>
  payload;

I opened https://github.com/swc-project/swc/pull/7242


Basic native support of MSAA for render targets

This change covers the basic case of passing in a sample count for render targets. It does not handle changing the sample count after initialization or multitargets.
This is just the JS changes. Additional native changes are needed for MSAA to work with render targets, but it does not require a protocol version update.
See https://forum.babylonjs.com/t/nativeengine-render-target-texture-not-working-with-msaa/42329.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14055/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14055/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14055/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14055/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14055/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14055/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14055/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14055/merge#BCU1XR#0

Visualization tests for webgl2 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14055/merge/testResults/webgl2/index.html
If tests were successful afterwards, this report might not be available anymore.

Visualization tests for webgl2 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14055/merge/testResults/webgl2/index.html
If tests were successful afterwards, this report might not be available anymore.


show diff on failure of pre-commit's tests

This will make sure that when a pre-commit test fails, it prints the diffs.
In this way people do not need to install anything, just fix the problems that are printed in the Travis CI report.

Codecov Report

Merging #1164 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1164   +/-   ##
=======================================
  Coverage   43.66%   43.66%
=======================================
  Files          32       32
  Lines        3570     3570
  Branches      579      579
=======================================
  Hits         1559     1559
  Misses       1869     1869
  Partials      142      142

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9cd7571...802ce0f. Read the comment docs.

Thank you for this commit. This is going to have more sense to use this pre-commit stuff. Not it becomes more usable.


Fix Account Metas Trait And Enable State Account Address Derivation

Closes https://github.com/project-serum/anchor/issues/405
Closes https://github.com/project-serum/anchor/issues/401

Need to run cargo fmt for the build to pass.


Sensor status is not consistent across sensor types

Feature Description
The Contact sensor displays status of closed, while the Leak sensor and the Smoke sensor don't display a status. Even the switch displays status of Off. All accessories should show status, when known, at least all contacts.

Successfully tested this enhancement with the following setup:
Homebridge Version: v1.8.5
Homebridge UI Version: v4.62.1-beta.20
Node JS Version: v22.9.0
Operating System: macOS Sequoia
Environment Info: Using hb-service
The state displays for both at-rest and triggered sensors and looks consistent across accessories.
Sensor default state

Sensor triggered

Closing ticket as feature implemented.


How serialize a list as an attribute

Hi,
I have a scenario where I have a key value pair.
I'd like to make that an attribute on an object but I don't know IF it should be on my object and I don't know how many might get added in the future hence the key value pair.
it's actually List<(string attribute, string value)> do you have an OOTB solution for that or do I need to write my own converter?

Sorry, I'm afraid serializing ValueTuples currently isn't implemented.
Besides that, I'm not sure whether this is what you're after:
public class SomeDemoClass
{
    public string Name { get; set; }

    [YAXCollection(YAXCollectionSerializationTypes.Serially, SeparateBy = ", ")]
    [YAXAttributeForClass]
    public List<string> AttributeValues { get; set; }

    public static SomeDemoClass GetSampleInstance()
    {
        var vt = new List<string>();
        vt.Add(("one|one-value"));
        vt.Add(("two|two-value"));
        vt.Add(("three|three-value"));
        vt.Add(("four|four-value"));
        var w = new SomeDemoClass
        {
            Name = "Some name",
            AttributeValues = vt
        };

        return w;
    }
}

var s = new YAXSerializer(typeof(SomeDemoClass));
var xml = s.Serialize(SomeDemoClass.GetSampleInstance());

This would serialize the list as an attribute of the containing class:
<SomeDemoClass AttributeValues="one|one-value, two|two-value, three|three-value, four|four-value">
  <Name>Some name</Name>
</SomeDemoClass>

I'm sorry, I should've added an example.
So what I'm trying to achieve is this:
public sealed class SomeModel {

    // Other props hidden for example
    public IReadonlyList<(string name, string value)> AdditionalAttributes {get;set;}
}

With this value:
var foo = new SomeModel {
    AdditionalAttributes = {
        ("qux", "4"),
        ("quo", "20")
    }
};

And I want this to translate to:
<SomeModel qux="4" quo="20">
    <!-- properties and children hidden for example -->
</SomeModel>

I think I have a solution for this, I was mostly just wondering if there's an OOTB attribute available but I don't think so from scanning the repo.
I'll post my solution if I test it successfully. Otherwise, I'll just have to have a model with all the possible attributes and set the ones I don't need to null I guess.

<SomeModel qux="4" quo="20">

Thanks for the clarification.
So you don't want to place all the attributes from the list, but just the ones you need ;-)
Yes, I'd be interested in how you finally solved that, including the ValueTuples.

That's a smart idea [YAXAttributeForClass, YAXCustomSerializer(typeof(AdditionalAttributesSerializer))] and "almost" out-of-the-box 😉.  Thanks for sharing!

Todo: Add @Marvin-Brouwer 's code to the samples of the Wiki.


Code review changes from #1032 Added feature for gravity based embedding - Issue #542

Squashed against upstream/suit and added the other code review changes.

Coverage increased (+0.01%) to 99.043% when pulling 5df9c579a793f9f8cbeddaece8eee7147380e1d4 on AzureByte:feature/embedgravityrebased2 into 1fec132dee6bf5fbfb6590da6dacd18f26b52311 on lovell:suit.

Thank you, I'll take a look at this later in the week.

@AzureByte Sorry it has taken me a while to get back to your useful addition. Are you able to update the target branch of the PR from suit to master?

Thank you Kenric, this will be in v0.19.0.


broken links in docs

BigchainDB version: latest
Operating System: /
Deployment Type: /
BigchainDB driver: no

Description
https://docs.bigchaindb.com/projects/server/en/latest/data-models/block-model.html
On this page, there are three links to IPDB readthedocs and none of them works
same goes for this page:
https://docs.bigchaindb.com/projects/server/en/latest/data-models/vote-model.html
Steps to Reproduce
None
What I Did
None

Good catch: those links point to URLs like https://the-ipdb-protocol.readthedocs.io/en/latest/crypto-hashes.html but they were changed to https://the-ipdb-transaction-spec.readthedocs.io/en/latest/common-operations/crypto-hashes.html
I will fix this.


LIBUSB_ERROR_BUSY Raspberry Pi 3

Firstable I had LIBUSB_ERROR_ACCESS that I fix adding permissions to usblib but now I have this error and I can't found out whats the reason because nobody uses this usb driver before my node server so I don't unsderstand.
Regards

I would also like a solution to this. I am getting this on the PiB 1

I did some research into this: The reason is that the pi attaches a kernel driver to connected devices. You need to check for a kernel driver and detach it before claiming the interface.
pseudo code:
device.open()
const deviceInterface = device.interfaces[0]

let driverAttached = false
if (printerInterface.isKernelDriverActive()) {
   driverAttached = true
   deviceInterface.detachKernelDriver()
}

deviceInterface.claim()

// ... use the device

deviceInterface.release(() => {
   if (driverAttached) {
      deviceInterface.attachKernelDriver()
   }

   device.close()
})

:+1: We should add a "Troubleshooting FAQ" section to the README with hints like this.

Closing in favor of #182


Fix whitespace issue

Replace example comment:
/*eslint-env node, mocha */

with:
/*eslint-env node, mocha */

Reason:
The example caused a linting error.
1:1   error  Expected space or tab after "/*" in comment  spaced-comment

I see that there are lots of other examples missing whitespace.
Example:
/*global var1, var2*/

I could update the PR to fix them all in case you would accept the PR. Or ist that on purpose?

Thanks for PR. Those comments only require space if the spaced-comment configured with always. I don't think there's a huge need to replace this style throughout the documentation.

Okay. just wondered because always is the default value
Fell free to close the PR :octocat:


Add bom in dolphinscheduler-datasource-databend

Purpose of the pull request

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Codecov Report

Merging #14408 (c7be456) into dev (9c92b4b) will decrease coverage by 0.01%.
The diff coverage is n/a.

:exclamation: Current head c7be456 differs from pull request most recent head 1e86459. Consider uploading reports for the commit 1e86459 to get more accurate results

@@             Coverage Diff              @@
##                dev   #14408      +/-   ##
============================================
- Coverage     38.49%   38.48%   -0.01%
+ Complexity     4561     4555       -6
============================================
  Files          1237     1237
  Lines         43537    43489      -48
  Branches       4815     4783      -32
============================================
- Hits          16758    16736      -22
+ Misses        24927    24902      -25
+ Partials       1852     1851       -1

see 40 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Update react router sidenav example

Description
Fixes wrong destructuring naming in the React Router side navigation example. This should be correct unless the example should rather be in the onChange={({event: e, item}) => { form.
Scope

[ ] Patch: Bug Fix
[ ] Minor: New Feature
[ ] Major: Breaking Change

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I am btw unable to set the label on this as is said in your contributing rules

Thank you for the fix! @aevarisak


Support sign in integer casting of strings minor BUG [#214] - Closed

Pocketpy main before the fixes
>>> a = int('-123')
Traceback (most recent call last):
  File "<stdin>", line 1
    a = int('-123')
ValueError: invalid literal for int(): '-123'
>>>
>>> a = int('+123')
Traceback (most recent call last):
  File "<stdin>", line 1
    a = int('+123')
ValueError: invalid literal for int(): '+123'

Pocketpy main after the fixes
>>> int('-123')
123
>>> int('+123')
123

AND ALL TESTS PASSED after running --> scripts/run_tests.py

The related issue was closed.


Remove -lgcc_s from the list of library dependencies in .pc file

When -lgcc_s is in the list of required libraries in .pc, it's impossible to avoid dependency to dynamic libgcc_s.so when linking gcc statically inside target binary using -static-libgcc option.

The issue doesn't appear when building libvvdec, but when building a project (application or library) that uses libvvdec and pkgconfig to find the dependency.
If you try to build a binary and link libvvdec statically, these dependencies specified in .pc file will be added:
Libs.private: -lstdc++ -lm -lgcc -lgcc -lgcc_s

When using -static-libgcc, the -lgcc dependency won't appear in target app/lib, but -lgcc_s will still be there.
It is enough to have only -lgcc in Libs.private. -lgcc_s is unnecessary because either libgcc.a or libgcc_s needs to be linked.
https://gcc.gnu.org/onlinedocs/gccint/Libgcc.html


how to set the default size like 1280*960 please guys help me

how to set the default size like 1280*960 how can i do this

CameraFragment cameraFragment = CameraFragment.newInstance(new Configuration.Builder()                 .setCamera(Configuration.CAMERA_FACE_FRONT)                 .setMediaQuality(Configuration.CHOOSE_MEDIA_QUALITY)                 .build());


Need bluepill support for XCode13.4.1

Team,
Our applications only runs on Xcode 13.4.1 and need bluepill support for XCode13.4.1.
It is bit urgent.
Could you please help me.

@nanwng I think it'd be possible to back port your fix for Xcode 14 to 13.4.1 no?

@nanwng I think it'd be possible to back port your fix for Xcode 14 to 13.4.1 no?

currently it is not possible

@ob @nanwng  Any help please.

#540 should fix this when it's merged into a branch...

#540 should fix this when it's merged into a branch...

Thanks @ob  Could you please merge and create release asap so that we can start using it.

I need to check with @chenxiao0228  to see where this is at. We'll have an answer tomorrow.

Just pushed the tags. Releases are available on Github. Will double check Cocoapods repo

pls try 5.11.1


Document usage of ReadSpreadsheet

At the moment this is more a question for which the answer should likely be public: is there any basic example out there of a basic spreadsheet format and the result it provides in person's properties when imported?
I've been shared some private example usage of compscript, but the data in spreadsheets have been appropriately omitted, and now I'm left with a few questions on the format I should target (because importing data dynamically sounds like a great idea for Euros ;)).
Let's take for instance the following data (csv, but separated by ';' intentionally, because of how I think values are parsed in the code):
identifier:string:wca_id;identifier:integer:user_id;property:list:scramble-events;property:string:team-kind;ignore:Some nice thing
2008VIRO01;;3x3,2x2;teams;titi
2008PIAU01;;5x5,2x2;teams;toto
;61698;;teams;tutu
2018GODI01;;;data-entry;tata

Reading from the source code, I would guess this results in adding the properties "scramble-events" and "team-kind", respectively holding an array of string and a string, that I would be able to query using respectively ArrayProperty("scramble-events") and StringProperty("team-kind")?
The "Some nice thing" column would simply be ignored.
Could you please confirm using this format is enough to identify whom to attach the data to based on the wca_id/user_id fields? (and does it matter if both of them are filled?)
What happens if one of the columns' header doesn't have the ignore:/identifier:/property: prefix?
For the record I still intend to run a test competition with a simplified example of basically everything, that could serve as a publicly available showcase of compscript (and for which I could make the spreadsheet used public, hence "fixing" this "issue".

I've played around a bit, and it turns out (quite logically) the identifiers need to exist in the person's data; I'll send a PR with a few changes related to authentication soon, but basically this seems to work as I wanted:
identifier:string:wcaId;identifier:number:wcaUserId;property:list:scramble-events;property:string:team-kind;ignore:Some nice thing
2008VIRO01;;3x3,2x2;teams;titi
2008PIAU01;;5x5,2x2;teams;toto
;61698;;teams;tutu
2018GODI01;;;data-entry;tata
2016LOPE37;;;orga;

Which can be used in a script like this (I've intentionally put the spreadsheet link as it is public):
ClearWCIF(true)

#https://docs.google.com/spreadsheets/d/1-TK-X69OjwYAnCzM_UfUCua1KAEQpU3zdJRdCAmz5Yw/edit?usp=sharing
ReadSpreadsheet("1-TK-X69OjwYAnCzM_UfUCua1KAEQpU3zdJRdCAmz5Yw")

Persons((StringProperty("team-kind") == "teams"))

ArrayProperty("scramble-events", 2008VIRO01)
Persons(In("3x3", ArrayProperty("scramble-events")))

Persons((StringProperty("team-kind") == "orga"))

Hey Philippe,
You've got it! Thanks for putting up with the lack of documentation :) A few details:

If there are multiple identifiers, it looks for which person matches the most. In our form we use 3 identifiers (name, email, WCA ID); these are all three that people should know. I didn't ask for WCA User ID since people don't use theirs regularly. So if I filled out "Timmm Reynolds /<EMAIL_ADDRESS>/ 2005REYN01", that should work; whereas if I put "Philippe Virouleau /<EMAIL_ADDRESS>/ 2005REYN01", that would fail because it would be a tie between 2 competitors.
The output of that function is a list of rows that it failed to parse, so you can go back in and fix them.
While testing on a dev export, this frequently failed because it doesn't have people's email addresses. So I made the error handling pretty resilient. But on the prod site, it fails a lot less often because it's using real email addresses -- that's another matching point :)
In our form, we had two header rows -- one for the formulaic header, one that Google Forms added

Columns without a header (or without one of the expected prefixes) are ignored.
In our form we used the following headers:
identifier:string:email
identifier:string:name
identifier:string:wcaId
property:number:attending (on a scale of 1-5 are you attending)
property:number:group-id (pick a group of people you'd like to be on a team with; the number goes in this column)
property:number:percent-judge (note that the code is resilient to these not adding up to 100)
property:number:percent-scrambler
property:number:percent-runner
property:list:puzzles-to-scramble
property:string:staff-team-form (the human-readable version of "what kind of staff are you", e.g. "Core Staff (including Stage Leads)". There was a separate "staff-team" property derived from this, that made it less verbose)

Let me know if you have any more questions :)

Thanks a whole lot for the answers and explanations!
It does explain some details of the code I didn't understand on the first read :)
I intend to do a proper competition example at the end of the month on a "small" competition to test out of few stuff for euros; I'll make sure to not include non public information and to share/document everything publicly and it should be more than enough for this issue :)


Pull request to DefinitelyTyped to include LTS for moment

https://github.com/borisyankov/DefinitelyTyped/pull/6109


TickCountWhenToKill appears to be populated incorrectly

https://github.com/jitbit/FastCache/blob/2a016db71fd766a49496d927c553fafec6a152a3/FastCache/FastCache.cs#L247
Isn't there a bug here? You're adding ttl.TotalMilliseconds to the current tick count, shouldn't you be adding ttl.Ticks?

Nope. It's a misleading name, the thing actually holds milliseconds.
https://learn.microsoft.com/en-us/dotnet/api/system.environment.tickcount64?view=net-8.0

Environment.TickCount64 Property
Gets the number OF MILLISECONDS elapsed since the system started.


Not updating .release-please-manifest.json

We use release-please to create releases for the Puppeteer project. The current structure is a mono repo so we use a configuration file  to express this.
This works well for the 3 packages that depend on each other  puppeteer, puppeteer-core, and @puppeteer/browsers.
But for the last one @puppeteer/ng-schematics we are seeing issue that the release does not update .release-please-manifest.json.
This can be observed on the latest PR - https://github.com/puppeteer/puppeteer/pull/11543.
If we do merge this PR without updating the manifest manually release-please will open a new one as the version differs with the manifest file. Observed:
Initial - https://github.com/puppeteer/puppeteer/pull/11496
A second one - https://github.com/puppeteer/puppeteer/pull/11508
The issue is not consistent. It doesn't fail all the time as you can see from https://github.com/puppeteer/puppeteer/pull/11488
Environment details

GitHub App

Steps to reproduce

Have not reproduced locally, but happy to follow up if instruction are provided.

I'm also seeing this issue and managed to reproduce locally with the CLI. If it'd be useful then I can try and push a reduced test case somewhere. I'm seeing it in both a brand new project and an existing one that I tried migrating to the latest version of Release Please.

@rowanmanning please do, I would be happy to take a look myself if I have a repo.

I'm also having the same issue with this. So I did some experiment and debugging on it.
I reproduced this problem with several repos linked below.

01Joseph-Hwang10/release-please-standalone-example#1
01Joseph-Hwang10/release-please-monorepo-with-root-example#1
01Joseph-Hwang10/release-please-monorepo-without-root-example#1

Turned out this problem could be reproduced on 01Joseph-Hwang10/release-please-standalone-example#1 and 01Joseph-Hwang10/release-please-monorepo-without-root-example#1.
Debugging on 01Joseph-Hwang10/release-please-standalone-example#1
As I first faced this issue in standalone node project environment, I did some debugging in my local machine with release-please CLI. I added some more console.logs in the source of release-please to figure out what's happening and what's wrong.
What I ran:
release-please release-pr --token="$GITHUB_TOKEN" --repo-url="https://github.com/01Joseph-Hwang10/release-please-standalone-example" --trace --dry-run

The below was the output. Note that there exist several >>>>>>>>>>>> START LOGS @ <class & method names> >>>>>>>>>>>> lines to express that this is console.log lines I added for debugging purposes.

Output

❯ Fetching release-please-config.json from branch main
❯ Fetching .release-please-manifest.json from branch main
✔ Building pull requests
✔ Building strategies by path
❯ .: node
❯ Fetching package.json from branch main
✔ Collecting release commit SHAs
❯ release search depth: 400
❯ Fetching releases with cursor undefined
⚠ Could not find releases.
⚠ Expected 1 releases, only found 0
⚠ Missing 1 paths: .
❯ looking for tagName: release-please-standalone-example-v0.1.0
⚠ Expected 1 releases, only found 0
✔ Collecting commits since all latest releases
❯ commit search depth: 500
❯ Set(0) {}
❯ Fetching merge commits on branch main with cursor: undefined
❯ Backfilling file list for commit: f4983bea3735836778edba610ef5f22645c10690
❯ Found 1 files
❯ Backfilling file list for commit: 37cfb3e5b46bd539ea9531906beff30af21e6212
❯ Found 5 files
✔ Splitting 2 commits by path
✔ No latest release found for path: ., component: release-please-standalone-example, but a previous version (0.1.0) was specified in the manifest.
✔ Building candidate release pull request for path: .
❯ type: node
❯ targetBranch: main
❯ commits: 2
⚠ No latest release pull request found.
✔ Considering: 2 commits
❯ component: release-please-standalone-example
❯ pull request title pattern: undefined
❯ running plugin: NodeWorkspace
✔ Running workspace plugin
✔ Found 1 in-scope releases
✔ Building list of all packages
❯ Found candidate pull request for path: .
❯ Fetching package.json from branch main
✔ Building dependency graph for 1 packages
✔ building graph order, existing package names: release-please-standalone-example
❯ visiting release-please-standalone-example, path:
❯ marking release-please-standalone-example as visited and adding release-please-standalone-example to order
✔ Updating 1 packages
❯ package: release-please-standalone-example
❯ version: 0.2.0 from release-please
✔ Updating existing candidate pull request for release-please-standalone-example, path: .
✔ Merging 1 in-scope candidates
✔ Merging 1 pull requests
>>>>>>>>>>>>>>>>>>>> START LOGS @ class Merge.run @ const updates >>>>>>>>>>>>>>>>>>>>
updates - merged:  [
  {
    path: 'package-lock.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: [Map] }
  },
  {
    path: 'npm-shrinkwrap.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: Map(0) {} }
  },
  {
    path: 'samples/package.json',
    createIfMissing: false,
    updater: SamplesPackageJson {
      version: [Version],
      versionsMap: undefined,
      packageName: 'release-please-standalone-example'
    }
  },
  {
    path: 'CHANGELOG.md',
    createIfMissing: true,
    updater: Changelog {
      version: [Version],
      versionsMap: undefined,
      changelogEntry: '## [0.2.0](https://github.com/01Joseph-Hwang10/release-please-standalone-example/compare/release-please-standalone-example-v0.1.0...release-please-standalone-example-v0.2.0) (2024-05-15)\n' +
        '\n' +
        '\n' +
        '### Features\n' +
        '\n' +
        '* some change ([f4983be](https://github.com/01Joseph-Hwang10/release-please-standalone-example/commit/f4983bea3735836778edba610ef5f22645c10690))',
      versionHeaderRegex: /\n###? v?[0-9[]/s
    }
  },
  {
    path: 'package.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  },
  {
    path: 'changelog.json',
    createIfMissing: false,
    updater: ChangelogJson {
      version: [Version],
      versionsMap: undefined,
      language: 'JAVASCRIPT',
      artifactName: 'release-please-standalone-example',
      commits: [Array]
    }
  },
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: ReleasePleaseManifest { version: [Version], versionsMap: [Map] }
  }
]
updates - merged - release-please-manifest:  [
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: ReleasePleaseManifest { version: [Version], versionsMap: [Map] }
  }
]
updates - merged - release-please-manifest - updater:  [
  ReleasePleaseManifest {
    version: Version {
      major: 0,
      minor: 2,
      patch: 0,
      preRelease: undefined,
      build: undefined
    },
    versionsMap: Map(1) { '.' => [Version] }
  }
]
<<<<<<<<<<<<<<<<<<<< END LOGS @ class Merge.run @ const updates <<<<<<<<<<<<<<<<<<<<
⚠ pullRequestTitlePattern miss the part of '${scope}'
⚠ pullRequestTitlePattern miss the part of '${component}'
⚠ pullRequestTitlePattern miss the part of '${version}'
>>>>>>>>>>>>>>>>>>>> START LOGS @ class WorkspacePlugin.run @ const newUpdates >>>>>>>>>>>>>>>>>>>>
newCandidates:  [
  {
    path: '.',
    pullRequest: {
      title: [PullRequestTitle],
      body: [PullRequestBody],
      updates: [Array],
      labels: [Array],
      headRefName: 'release-please--branches--main',
      draft: false
    },
    config: { releaseType: 'node' }
  }
]
newUpdates:  [
  {
    path: 'package-lock.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: [Map] }
  },
  {
    path: 'npm-shrinkwrap.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: Map(0) {} }
  },
  {
    path: 'samples/package.json',
    createIfMissing: false,
    updater: SamplesPackageJson {
      version: [Version],
      versionsMap: undefined,
      packageName: 'release-please-standalone-example'
    }
  },
  {
    path: 'CHANGELOG.md',
    createIfMissing: true,
    updater: Changelog {
      version: [Version],
      versionsMap: undefined,
      changelogEntry: '## [0.2.0](https://github.com/01Joseph-Hwang10/release-please-standalone-example/compare/release-please-standalone-example-v0.1.0...release-please-standalone-example-v0.2.0) (2024-05-15)\n' +
        '\n' +
        '\n' +
        '### Features\n' +
        '\n' +
        '* some change ([f4983be](https://github.com/01Joseph-Hwang10/release-please-standalone-example/commit/f4983bea3735836778edba610ef5f22645c10690))',
      versionHeaderRegex: /\n###? v?[0-9[]/s
    }
  },
  {
    path: 'package.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  },
  {
    path: 'changelog.json',
    createIfMissing: false,
    updater: ChangelogJson {
      version: [Version],
      versionsMap: undefined,
      language: 'JAVASCRIPT',
      artifactName: 'release-please-standalone-example',
      commits: [Array]
    }
  },
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: ReleasePleaseManifest { version: [Version], versionsMap: [Map] }
  }
]
newUpdates - release-please-manifest:  [
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: ReleasePleaseManifest { version: [Version], versionsMap: [Map] }
  }
]
newUpdates - release-please-manifest - updater:  [
  ReleasePleaseManifest {
    version: Version {
      major: 0,
      minor: 2,
      patch: 0,
      preRelease: undefined,
      build: undefined
    },
    versionsMap: Map(1) { '.' => [Version] }
  }
]
newCandidates[0].pullRequest.version:  undefined
updatedPathVersions:  Map(0) {}
✔ Post-processing 1 in-scope candidates
newUpdates - release-please-manifest:  [
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: ReleasePleaseManifest { version: [Version], versionsMap: [Map] }
  },
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: ReleasePleaseManifest {
      version: undefined,
      versionsMap: Map(0) {}
    }
  }
]
newUpdates - release-please-manifest - updater [
  ReleasePleaseManifest {
    version: Version {
      major: 0,
      minor: 2,
      patch: 0,
      preRelease: undefined,
      build: undefined
    },
    versionsMap: Map(1) { '.' => [Version] }
  },
  ReleasePleaseManifest { version: undefined, versionsMap: Map(0) {} }
]
<<<<<<<<<<<<<<<<<<<< END LOGS @ class WorkspacePlugin.run @ const newUpdates <<<<<<<<<<<<<<<<<<<<
Would open 1 pull requests
fork: false
title: chore: release main
branch: release-please--branches--main
draft: false
body: :robot: I have created a release *beep* *boop*
---

<details><summary>release-please-standalone-example: 0.2.0</summary>

## [0.2.0](https://github.com/01Joseph-Hwang10/release-please-standalone-example/compare/release-please-standalone-example-v0.1.0...release-please-standalone-example-v0.2.0) (2024-05-15)

### Features

* some change ([f4983be](https://github.com/01Joseph-Hwang10/release-please-standalone-example/commit/f4983bea3735836778edba610ef5f22645c10690))
</details>

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
updates: 8
❯ Fetching package-lock.json from branch main
⚠ file package-lock.json did not exist
❯ Fetching npm-shrinkwrap.json from branch main
⚠ file npm-shrinkwrap.json did not exist
❯ Fetching samples/package.json from branch main
⚠ file samples/package.json did not exist
❯ Fetching CHANGELOG.md from branch main
>>>>>>>>>>>>>>>>>>>> START LOGS @ class Github.buildChangeSet @ const contentText >>>>>>>>>>>>>>>>>>>>
content: undefined
contextText:  undefined
<<<<<<<<<<<<<<<<<<<< END LOGS @ class Github.buildChangeSet @ const contentText <<<<<<<<<<<<<<<<<<<<
❯ Fetching package.json from branch main
>>>>>>>>>>>>>>>>>>>> START LOGS @ class Github.buildChangeSet @ const contentText >>>>>>>>>>>>>>>>>>>>
content: {
  sha: '2d7bafc1d00594641d278152b5c619722da758d2',
  mode: '100644',
  content: 'ewogICJuYW1lIjogInJlbGVhc2UtcGxlYXNlLXN0YW5kYWxvbmUtZXhhbXBs\n' +
    'ZSIsCiAgInZlcnNpb24iOiAiMC4xLjAiLAogICJkZXNjcmlwdGlvbiI6ICIi\n' +
    'LAogICJsaWNlbnNlIjogIklTQyIKfQ==\n',
  parsedContent: '{\n' +
    '  "name": "release-please-standalone-example",\n' +
    '  "version": "0.1.0",\n' +
    '  "description": "",\n' +
    '  "license": "ISC"\n' +
    '}'
}
contextText:  {
  "name": "release-please-standalone-example",
  "version": "0.1.0",
  "description": "",
  "license": "ISC"
}
<<<<<<<<<<<<<<<<<<<< END LOGS @ class Github.buildChangeSet @ const contentText <<<<<<<<<<<<<<<<<<<<
✔ updating from 0.1.0 to 0.2.0
✔ updating from 0.2.0 to 0.2.0
❯ Fetching changelog.json from branch main
⚠ file changelog.json did not exist
❯ Fetching .release-please-manifest.json from branch main
>>>>>>>>>>>>>>>>>>>> START LOGS @ class Github.buildChangeSet @ const contentText >>>>>>>>>>>>>>>>>>>>
content: {
  sha: '3d2ac0bdd2ec1cd2d5891da48ae2a84ed7ebc9fe',
  mode: '100644',
  content: 'ewogICIuIjogIjAuMS4wIgp9\n',
  parsedContent: '{\n  ".": "0.1.0"\n}'
}
contextText:  {
  ".": "0.1.0"
}
<<<<<<<<<<<<<<<<<<<< END LOGS @ class Github.buildChangeSet @ const contentText <<<<<<<<<<<<<<<<<<<<
>>>>>>>>>>>>>>>>>>>> START LOGS @ class ReleasePleaseManifest.updateContent >>>>>>>>>>>>>>>>>>>>
content:  {
  ".": "0.1.0"
}
this.versionsMap:  Map(1) {
  '.' => Version {
    major: 0,
    minor: 2,
    patch: 0,
    preRelease: undefined,
    build: undefined
  }
}
parsed - updated:  { '.': '0.2.0' }
<<<<<<<<<<<<<<<<<<<< END LOGS @ class ReleasePleaseManifest.updateContent <<<<<<<<<<<<<<<<<<<<
❯ Fetching .release-please-manifest.json from branch main
>>>>>>>>>>>>>>>>>>>> START LOGS @ class Github.buildChangeSet @ const contentText >>>>>>>>>>>>>>>>>>>>
content: {
  sha: '3d2ac0bdd2ec1cd2d5891da48ae2a84ed7ebc9fe',
  mode: '100644',
  content: 'ewogICIuIjogIjAuMS4wIgp9\n',
  parsedContent: '{\n  ".": "0.1.0"\n}'
}
contextText:  {
  ".": "0.1.0"
}
<<<<<<<<<<<<<<<<<<<< END LOGS @ class Github.buildChangeSet @ const contentText <<<<<<<<<<<<<<<<<<<<
>>>>>>>>>>>>>>>>>>>> START LOGS @ class ReleasePleaseManifest.updateContent >>>>>>>>>>>>>>>>>>>>
content:  {
  ".": "0.1.0"
}
this.versionsMap:  Map(0) {}
parsed - updated:  { '.': '0.1.0' }
<<<<<<<<<<<<<<<<<<<< END LOGS @ class ReleasePleaseManifest.updateContent <<<<<<<<<<<<<<<<<<<<
  package-lock.json:  [class PackageLockJson]
no change found for package-lock.json
  npm-shrinkwrap.json:  [class PackageLockJson]
no change found for npm-shrinkwrap.json
  samples/package.json:  [class SamplesPackageJson extends DefaultUpdater]
no change found for samples/package.json
  CHANGELOG.md:  [class Changelog extends DefaultUpdater]
Index: CHANGELOG.md
===================================================================
--- CHANGELOG.md
+++ CHANGELOG.md
@@ -0,0 +1,8 @@
+# Changelog
+
+## [0.2.0](https://github.com/01Joseph-Hwang10/release-please-standalone-example/compare/release-please-standalone-example-v0.1.0...release-please-standalone-example-v0.2.0) (2024-05-15)
+
+
+### Features
+
+* some change ([f4983be](https://github.com/01Joseph-Hwang10/release-please-standalone-example/commit/f4983bea3735836778edba610ef5f22645c10690))

  package.json:  [class CompositeUpdater]
Index: package.json
===================================================================
--- package.json
+++ package.json
@@ -1,6 +1,6 @@
 {
   "name": "release-please-standalone-example",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "",
   "license": "ISC"
 }
\ No newline at end of file

  changelog.json:  [class ChangelogJson extends DefaultUpdater]
no change found for changelog.json
  .release-please-manifest.json:  [class ReleasePleaseManifest extends DefaultUpdater]
Index: .release-please-manifest.json
===================================================================
--- .release-please-manifest.json
+++ .release-please-manifest.json

  .release-please-manifest.json:  [class ReleasePleaseManifest extends DefaultUpdater]
Index: .release-please-manifest.json
===================================================================
--- .release-please-manifest.json
+++ .release-please-manifest.json

I found out @ class ReleasePleaseManifest.updateContent part, which appears 2 times among the output,
and found out each of those are

from releasePullRequest.updates.push(...) at class Manifest.buildPullRequests and
from newUpdates.push(...) at abstract class WorkspacePlugin.run.

Those updates are pushed in order I enumerated above.
So the firstly pushed release please manifest update corresponds with the logs:
>>>>>>>>>>>>>>>>>>>> START LOGS @ class ReleasePleaseManifest.updateContent >>>>>>>>>>>>>>>>>>>>
content:  {
  ".": "0.1.0"
}
this.versionsMap:  Map(1) {
  '.' => Version {
    major: 0,
    minor: 2,
    patch: 0,
    preRelease: undefined,
    build: undefined
  }
}
parsed - updated:  { '.': '0.2.0' }
<<<<<<<<<<<<<<<<<<<< END LOGS @ class ReleasePleaseManifest.updateContent <<<<<<<<<<<<<<<<<<<<

and the secondly pushed release please manifest update corresponds with the logs:
>>>>>>>>>>>>>>>>>>>> START LOGS @ class ReleasePleaseManifest.updateContent >>>>>>>>>>>>>>>>>>>>
content:  {
  ".": "0.1.0"
}
this.versionsMap:  Map(0) {}
parsed - updated:  { '.': '0.1.0' }
<<<<<<<<<<<<<<<<<<<< END LOGS @ class ReleasePleaseManifest.updateContent <<<<<<<<<<<<<<<<<<<<

And seems like those updates are performed independently. This means that each updater modifies original source file at the remote repository, not modifies whatever it is modified by the previous updater. We can notice, in the end, 2 updaters exist at the end of the entire class Manifest.buildPullRequests run.
# ...
newUpdates - release-please-manifest:  [
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: ReleasePleaseManifest { version: [Version], versionsMap: [Map] }
  },
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: ReleasePleaseManifest {
      version: undefined,
      versionsMap: Map(0) {}
    }
  }
]
newUpdates - release-please-manifest - updater [
  ReleasePleaseManifest {
    version: Version {
      major: 0,
      minor: 2,
      patch: 0,
      preRelease: undefined,
      build: undefined
    },
    versionsMap: Map(1) { '.' => [Version] }
  },
  ReleasePleaseManifest { version: undefined, versionsMap: Map(0) {} }
]
<<<<<<<<<<<<<<<<<<<< END LOGS @ class WorkspacePlugin.run @ const newUpdates <<<<<<<<<<<<<<<<<<<<

In sum, it appears that secondly pushed release please manifest update by abstract class WorkspacePlugin
overrides the firstly pushed update which correctly bumps the version.
Possible Solution I found
Possible solution I found after the digging process above, I successfully bumped the version by changing:
// https://github1s.com/googleapis/release-please/blob/main/src/plugins/workspace.ts
export abstract class WorkspacePlugin<T> extends ManifestPlugin {
  /* ... */
  async run(/* ... */): /* ... */ {
    /* ... */
    const newUpdates = newCandidates[0].pullRequest.updates;
    newUpdates.push({
      path: this.manifestPath,
      createIfMissing: false,
      updater: new ReleasePleaseManifest({
        version: newCandidates[0].pullRequest.version!,
        versionsMap: updatedPathVersions,
      }),
    });
    /* ... */
  }
  /* ... */
}

to:
// https://github1s.com/googleapis/release-please/blob/main/src/plugins/workspace.ts
export abstract class WorkspacePlugin<T> extends ManifestPlugin {
  /* ... */
  async run(/* ... */): /* ... */ {
    /* ... */
    const newUpdates = newCandidates[0].pullRequest.updates;
    const releasePleaseManifestUpdates = newUpdates.filter(
      (update) => update.path === this.manifestPath
    );
    if (releasePleaseManifestUpdates.length === 0) {
      newUpdates.push({
        path: this.manifestPath,
        createIfMissing: false,
        updater: new ReleasePleaseManifest({
          version: newCandidates[0].pullRequest.version!,
          versionsMap: updatedPathVersions,
        }),
      });
    }
    /* ... */
  }
  /* ... */
}

which correctly update .release-please-manifest.json and yields:

Output

❯ Fetching release-please-config.json from branch main
❯ Fetching .release-please-manifest.json from branch main
✔ Building pull requests
✔ Building strategies by path
❯ .: node
❯ Fetching package.json from branch main
✔ Collecting release commit SHAs
❯ release search depth: 400
❯ Fetching releases with cursor undefined
⚠ Could not find releases.
⚠ Expected 1 releases, only found 0
⚠ Missing 1 paths: .
❯ looking for tagName: release-please-standalone-example-v0.1.0
⚠ Expected 1 releases, only found 0
✔ Collecting commits since all latest releases
❯ commit search depth: 500
❯ Set(0) {}
❯ Fetching merge commits on branch main with cursor: undefined
❯ Backfilling file list for commit: f4983bea3735836778edba610ef5f22645c10690
❯ Found 1 files
❯ Backfilling file list for commit: 37cfb3e5b46bd539ea9531906beff30af21e6212
❯ Found 5 files
✔ Splitting 2 commits by path
✔ No latest release found for path: ., component: release-please-standalone-example, but a previous version (0.1.0) was specified in the manifest.
✔ Building candidate release pull request for path: .
❯ type: node
❯ targetBranch: main
❯ commits: 2
⚠ No latest release pull request found.
✔ Considering: 2 commits
❯ component: release-please-standalone-example
❯ pull request title pattern: undefined
❯ running plugin: NodeWorkspace
✔ Running workspace plugin
✔ Found 1 in-scope releases
✔ Building list of all packages
❯ Found candidate pull request for path: .
❯ Fetching package.json from branch main
✔ Building dependency graph for 1 packages
✔ building graph order, existing package names: release-please-standalone-example
❯ visiting release-please-standalone-example, path:
❯ marking release-please-standalone-example as visited and adding release-please-standalone-example to order
✔ Updating 1 packages
❯ package: release-please-standalone-example
❯ version: 0.2.0 from release-please
✔ Updating existing candidate pull request for release-please-standalone-example, path: .
✔ Merging 1 in-scope candidates
✔ Merging 1 pull requests
⚠ pullRequestTitlePattern miss the part of '${scope}'
⚠ pullRequestTitlePattern miss the part of '${component}'
⚠ pullRequestTitlePattern miss the part of '${version}'
✔ Post-processing 1 in-scope candidates
Would open 1 pull requests
fork: false
title: chore: release main
branch: release-please--branches--main
draft: false
body: :robot: I have created a release *beep* *boop*
---

<details><summary>release-please-standalone-example: 0.2.0</summary>

## [0.2.0](https://github.com/01Joseph-Hwang10/release-please-standalone-example/compare/release-please-standalone-example-v0.1.0...release-please-standalone-example-v0.2.0) (2024-05-15)

### Features

* some change ([f4983be](https://github.com/01Joseph-Hwang10/release-please-standalone-example/commit/f4983bea3735836778edba610ef5f22645c10690))
</details>

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
updates: 7
❯ Fetching package-lock.json from branch main
⚠ file package-lock.json did not exist
❯ Fetching npm-shrinkwrap.json from branch main
⚠ file npm-shrinkwrap.json did not exist
❯ Fetching samples/package.json from branch main
⚠ file samples/package.json did not exist
❯ Fetching CHANGELOG.md from branch main
❯ Fetching package.json from branch main
✔ updating from 0.1.0 to 0.2.0
✔ updating from 0.2.0 to 0.2.0
❯ Fetching changelog.json from branch main
⚠ file changelog.json did not exist
❯ Fetching .release-please-manifest.json from branch main
  package-lock.json:  [class PackageLockJson]
no change found for package-lock.json
  npm-shrinkwrap.json:  [class PackageLockJson]
no change found for npm-shrinkwrap.json
  samples/package.json:  [class SamplesPackageJson extends DefaultUpdater]
no change found for samples/package.json
  CHANGELOG.md:  [class Changelog extends DefaultUpdater]
Index: CHANGELOG.md
===================================================================
--- CHANGELOG.md
+++ CHANGELOG.md
@@ -0,0 +1,8 @@
+# Changelog
+
+## [0.2.0](https://github.com/01Joseph-Hwang10/release-please-standalone-example/compare/release-please-standalone-example-v0.1.0...release-please-standalone-example-v0.2.0) (2024-05-15)
+
+
+### Features
+
+* some change ([f4983be](https://github.com/01Joseph-Hwang10/release-please-standalone-example/commit/f4983bea3735836778edba610ef5f22645c10690))

  package.json:  [class CompositeUpdater]
Index: package.json
===================================================================
--- package.json
+++ package.json
@@ -1,6 +1,6 @@
 {
   "name": "release-please-standalone-example",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "",
   "license": "ISC"
 }
\ No newline at end of file

  changelog.json:  [class ChangelogJson extends DefaultUpdater]
no change found for changelog.json
  .release-please-manifest.json:  [class ReleasePleaseManifest extends DefaultUpdater]
Index: .release-please-manifest.json
===================================================================
--- .release-please-manifest.json
+++ .release-please-manifest.json
@@ -1,3 +1,3 @@
 {
-  ".": "0.1.0"
+  ".": "0.2.0"
 }
\ No newline at end of file

But I don't sure if this change stands against to the original intention, if there exists.
Please let me know if that update push made in abstract class WorkspacePlugin.run cannot be omitted conditionally and should always be pushed.
Compare Case: Debugging on [01Joseph-Hwang10/release-please-with-root-example#1]
As a compare case, where the updates of .release-please-manifest.json correctly happened, I also delved into the case of [01Joseph-Hwang10/release-please-with-root-example#1].
I ran:
release-please release-pr --token="$GITHUB_TOKEN" --repo-url="https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example" --trace --dry-run

which yielded:

Output

❯ Fetching release-please-config.json from branch main
❯ Fetching .release-please-manifest.json from branch main
✔ Building pull requests
✔ Building strategies by path
❯ .: node
❯ packages/a: node
❯ Fetching package.json from branch main
❯ Fetching packages/a/package.json from branch main
✔ Collecting release commit SHAs
❯ release search depth: 400
❯ Fetching releases with cursor undefined
⚠ Could not find releases.
⚠ Expected 2 releases, only found 0
⚠ Missing 2 paths: .,packages/a
❯ looking for tagName: release-please-monorepo-with-root-example-v0.1.0
❯ looking for tagName: a-v0.0.1
⚠ Expected 2 releases, only found 0
✔ Collecting commits since all latest releases
❯ commit search depth: 500
❯ Set(0) {}
❯ Fetching merge commits on branch main with cursor: undefined
❯ Backfilling file list for commit: ef77e163205409883c8fd87f2d3e456d43dc3f99
❯ Found 1 files
❯ Backfilling file list for commit: 00abf7d7d524a75d7a52c08f72aa3eec4851074b
❯ Found 1 files
❯ Backfilling file list for commit: 9766cf3b69775c6eddf29f647e439c254723aaf6
❯ Found 7 files
✔ Splitting 3 commits by path
✔ No latest release found for path: ., component: release-please-monorepo-with-root-example, but a previous version (0.1.0) was specified in the manifest.
✔ No latest release found for path: packages/a, component: a, but a previous version (0.0.1) was specified in the manifest.
✔ Building candidate release pull request for path: .
❯ type: node
❯ targetBranch: main
❯ commits: 2
⚠ No latest release pull request found.
✔ Considering: 2 commits
❯ component: release-please-monorepo-with-root-example
❯ pull request title pattern: undefined
✔ Building candidate release pull request for path: packages/a
❯ type: node
❯ targetBranch: main
❯ commits: 2
⚠ No latest release pull request found.
✔ Considering: 2 commits
❯ component: a
❯ pull request title pattern: undefined
❯ running plugin: NodeWorkspace
✔ Running workspace plugin
✔ Found 2 in-scope releases
✔ Building list of all packages
❯ Found candidate pull request for path: .
❯ Fetching package.json from branch main
❯ Found candidate pull request for path: packages/a
❯ Fetching packages/a/package.json from branch main
✔ Building dependency graph for 2 packages
✔ building graph order, existing package names: release-please-monorepo-with-root-example,a
❯ visiting release-please-monorepo-with-root-example, path:
❯ marking release-please-monorepo-with-root-example as visited and adding release-please-monorepo-with-root-example to order
❯ visiting a, path:
❯ marking a as visited and adding a to order
✔ Updating 2 packages
❯ package: a
❯ version: 0.1.0 from release-please
❯ package: release-please-monorepo-with-root-example
❯ version: 0.2.0 from release-please
✔ Updating existing candidate pull request for a, path: packages/a
✔ Updating existing candidate pull request for release-please-monorepo-with-root-example, path: .
✔ Merging 2 in-scope candidates
✔ Merging 2 pull requests
>>>>>>>>>>>>>>>>>>>> START LOGS @ class Merge.run @ const updates >>>>>>>>>>>>>>>>>>>>
updates - merged:  [
  {
    path: 'packages/a/package-lock.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: [Map] }
  },
  {
    path: 'packages/a/npm-shrinkwrap.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: Map(0) {} }
  },
  {
    path: 'packages/a/samples/package.json',
    createIfMissing: false,
    updater: SamplesPackageJson {
      version: [Version],
      versionsMap: undefined,
      packageName: 'a'
    }
  },
  {
    path: 'packages/a/CHANGELOG.md',
    createIfMissing: true,
    updater: Changelog {
      version: [Version],
      versionsMap: undefined,
      changelogEntry: '## [0.1.0](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/compare/a-v0.0.1...a-v0.1.0) (2024-05-15)\n' +
        '\n' +
        '\n' +
        '### Features\n' +
        '\n' +
        '* **a:** some change ([00abf7d](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/commit/00abf7d7d524a75d7a52c08f72aa3eec4851074b))',
      versionHeaderRegex: /\n###? v?[0-9[]/s
    }
  },
  {
    path: 'packages/a/package.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  },
  {
    path: 'changelog.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  },
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  },
  {
    path: 'package-lock.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: [Map] }
  },
  {
    path: 'npm-shrinkwrap.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: Map(0) {} }
  },
  {
    path: 'samples/package.json',
    createIfMissing: false,
    updater: SamplesPackageJson {
      version: [Version],
      versionsMap: undefined,
      packageName: 'release-please-monorepo-with-root-example'
    }
  },
  {
    path: 'CHANGELOG.md',
    createIfMissing: true,
    updater: Changelog {
      version: [Version],
      versionsMap: undefined,
      changelogEntry: '## [0.2.0](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/compare/release-please-monorepo-with-root-example-v0.1.0...release-please-monorepo-with-root-example-v0.2.0) (2024-05-15)\n' +
        '\n' +
        '\n' +
        '### Features\n' +
        '\n' +
        '* some change ([ef77e16](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/commit/ef77e163205409883c8fd87f2d3e456d43dc3f99))',
      versionHeaderRegex: /\n###? v?[0-9[]/s
    }
  },
  {
    path: 'package.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  }
]
updates - merged - release-please-manifest:  [
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  }
]
updates - merged - release-please-manifest - updater:  [
  CompositeUpdater {
    updaters: [ [ReleasePleaseManifest], [ReleasePleaseManifest] ]
  }
]
<<<<<<<<<<<<<<<<<<<< END LOGS @ class Merge.run @ const updates <<<<<<<<<<<<<<<<<<<<
⚠ pullRequestTitlePattern miss the part of '${scope}'
⚠ pullRequestTitlePattern miss the part of '${component}'
⚠ pullRequestTitlePattern miss the part of '${version}'
>>>>>>>>>>>>>>>>>>>> START LOGS @ class WorkspacePlugin.run @ const newUpdates >>>>>>>>>>>>>>>>>>>>
newCandidates:  [
  {
    path: '.',
    pullRequest: {
      title: [PullRequestTitle],
      body: [PullRequestBody],
      updates: [Array],
      labels: [Array],
      headRefName: 'release-please--branches--main',
      draft: false
    },
    config: { releaseType: 'node' }
  }
]
newUpdates:  [
  {
    path: 'packages/a/package-lock.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: [Map] }
  },
  {
    path: 'packages/a/npm-shrinkwrap.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: Map(0) {} }
  },
  {
    path: 'packages/a/samples/package.json',
    createIfMissing: false,
    updater: SamplesPackageJson {
      version: [Version],
      versionsMap: undefined,
      packageName: 'a'
    }
  },
  {
    path: 'packages/a/CHANGELOG.md',
    createIfMissing: true,
    updater: Changelog {
      version: [Version],
      versionsMap: undefined,
      changelogEntry: '## [0.1.0](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/compare/a-v0.0.1...a-v0.1.0) (2024-05-15)\n' +
        '\n' +
        '\n' +
        '### Features\n' +
        '\n' +
        '* **a:** some change ([00abf7d](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/commit/00abf7d7d524a75d7a52c08f72aa3eec4851074b))',
      versionHeaderRegex: /\n###? v?[0-9[]/s
    }
  },
  {
    path: 'packages/a/package.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  },
  {
    path: 'changelog.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  },
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  },
  {
    path: 'package-lock.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: [Map] }
  },
  {
    path: 'npm-shrinkwrap.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: Map(0) {} }
  },
  {
    path: 'samples/package.json',
    createIfMissing: false,
    updater: SamplesPackageJson {
      version: [Version],
      versionsMap: undefined,
      packageName: 'release-please-monorepo-with-root-example'
    }
  },
  {
    path: 'CHANGELOG.md',
    createIfMissing: true,
    updater: Changelog {
      version: [Version],
      versionsMap: undefined,
      changelogEntry: '## [0.2.0](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/compare/release-please-monorepo-with-root-example-v0.1.0...release-please-monorepo-with-root-example-v0.2.0) (2024-05-15)\n' +
        '\n' +
        '\n' +
        '### Features\n' +
        '\n' +
        '* some change ([ef77e16](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/commit/ef77e163205409883c8fd87f2d3e456d43dc3f99))',
      versionHeaderRegex: /\n###? v?[0-9[]/s
    }
  },
  {
    path: 'package.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  }
]
newUpdates - release-please-manifest:  [
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  }
]
newUpdates - release-please-manifest - updater:  [
  CompositeUpdater {
    updaters: [ [ReleasePleaseManifest], [ReleasePleaseManifest] ]
  }
]
newCandidates[0].pullRequest.version:  undefined
updatedPathVersions:  Map(0) {}
✔ Post-processing 1 in-scope candidates
newUpdates - release-please-manifest:  [
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  },
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: ReleasePleaseManifest {
      version: undefined,
      versionsMap: Map(0) {}
    }
  }
]
newUpdates - release-please-manifest - updater [
  CompositeUpdater {
    updaters: [ [ReleasePleaseManifest], [ReleasePleaseManifest] ]
  },
  ReleasePleaseManifest { version: undefined, versionsMap: Map(0) {} }
]
<<<<<<<<<<<<<<<<<<<< END LOGS @ class WorkspacePlugin.run @ const newUpdates <<<<<<<<<<<<<<<<<<<<
❯ running plugin: Merge
✔ Merging 1 pull requests
>>>>>>>>>>>>>>>>>>>> START LOGS @ class Merge.run @ const updates >>>>>>>>>>>>>>>>>>>>
updates - merged:  [
  {
    path: 'packages/a/package-lock.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: [Map] }
  },
  {
    path: 'packages/a/npm-shrinkwrap.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: Map(0) {} }
  },
  {
    path: 'packages/a/samples/package.json',
    createIfMissing: false,
    updater: SamplesPackageJson {
      version: [Version],
      versionsMap: undefined,
      packageName: 'a'
    }
  },
  {
    path: 'packages/a/CHANGELOG.md',
    createIfMissing: true,
    updater: Changelog {
      version: [Version],
      versionsMap: undefined,
      changelogEntry: '## [0.1.0](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/compare/a-v0.0.1...a-v0.1.0) (2024-05-15)\n' +
        '\n' +
        '\n' +
        '### Features\n' +
        '\n' +
        '* **a:** some change ([00abf7d](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/commit/00abf7d7d524a75d7a52c08f72aa3eec4851074b))',
      versionHeaderRegex: /\n###? v?[0-9[]/s
    }
  },
  {
    path: 'packages/a/package.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  },
  {
    path: 'changelog.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  },
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  },
  {
    path: 'package-lock.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: [Map] }
  },
  {
    path: 'npm-shrinkwrap.json',
    createIfMissing: false,
    updater: PackageLockJson { version: [Version], versionsMap: Map(0) {} }
  },
  {
    path: 'samples/package.json',
    createIfMissing: false,
    updater: SamplesPackageJson {
      version: [Version],
      versionsMap: undefined,
      packageName: 'release-please-monorepo-with-root-example'
    }
  },
  {
    path: 'CHANGELOG.md',
    createIfMissing: true,
    updater: Changelog {
      version: [Version],
      versionsMap: undefined,
      changelogEntry: '## [0.2.0](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/compare/release-please-monorepo-with-root-example-v0.1.0...release-please-monorepo-with-root-example-v0.2.0) (2024-05-15)\n' +
        '\n' +
        '\n' +
        '### Features\n' +
        '\n' +
        '* some change ([ef77e16](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/commit/ef77e163205409883c8fd87f2d3e456d43dc3f99))',
      versionHeaderRegex: /\n###? v?[0-9[]/s
    }
  },
  {
    path: 'package.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  }
]
updates - merged - release-please-manifest:  [
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  }
]
updates - merged - release-please-manifest - updater:  [
  CompositeUpdater {
    updaters: [ [CompositeUpdater], [ReleasePleaseManifest] ]
  }
]
<<<<<<<<<<<<<<<<<<<< END LOGS @ class Merge.run @ const updates <<<<<<<<<<<<<<<<<<<<
⚠ pullRequestTitlePattern miss the part of '${scope}'
⚠ pullRequestTitlePattern miss the part of '${component}'
⚠ pullRequestTitlePattern miss the part of '${version}'
Would open 1 pull requests
fork: false
title: chore: release main
branch: release-please--branches--main
draft: false
body: :robot: I have created a release *beep* *boop*
---

<details><summary>a: 0.1.0</summary>

## [0.1.0](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/compare/a-v0.0.1...a-v0.1.0) (2024-05-15)

### Features

* **a:** some change ([00abf7d](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/commit/00abf7d7d524a75d7a52c08f72aa3eec4851074b))
</details>

<details><summary>release-please-monorepo-with-root-example: 0.2.0</summary>

## [0.2.0](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/compare/release-please-monorepo-with-root-example-v0.1.0...release-please-monorepo-with-root-example-v0.2.0) (2024-05-15)

### Features

* some change ([ef77e16](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/commit/ef77e163205409883c8fd87f2d3e456d43dc3f99))
</details>

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
updates: 12
❯ Fetching packages/a/package-lock.json from branch main
⚠ file packages/a/package-lock.json did not exist
❯ Fetching packages/a/npm-shrinkwrap.json from branch main
⚠ file packages/a/npm-shrinkwrap.json did not exist
❯ Fetching packages/a/samples/package.json from branch main
⚠ file packages/a/samples/package.json did not exist
❯ Fetching packages/a/CHANGELOG.md from branch main
>>>>>>>>>>>>>>>>>>>> START LOGS @ class Github.buildChangeSet @ const contentText >>>>>>>>>>>>>>>>>>>>
content: undefined
contextText:  undefined
<<<<<<<<<<<<<<<<<<<< END LOGS @ class Github.buildChangeSet @ const contentText <<<<<<<<<<<<<<<<<<<<
❯ Fetching packages/a/package.json from branch main
>>>>>>>>>>>>>>>>>>>> START LOGS @ class Github.buildChangeSet @ const contentText >>>>>>>>>>>>>>>>>>>>
content: {
  sha: '705144843f18e496e71e4fb37e84b92947055238',
  mode: '100644',
  content: 'ewogICJuYW1lIjogImEiLAogICJ2ZXJzaW9uIjogIjAuMC4xIiwKICAiZGVz\n' +
    'Y3JpcHRpb24iOiAiIiwKICAibGljZW5zZSI6ICJJU0MiCn0=\n',
  parsedContent: '{\n' +
    '  "name": "a",\n' +
    '  "version": "0.0.1",\n' +
    '  "description": "",\n' +
    '  "license": "ISC"\n' +
    '}'
}
contextText:  {
  "name": "a",
  "version": "0.0.1",
  "description": "",
  "license": "ISC"
}
<<<<<<<<<<<<<<<<<<<< END LOGS @ class Github.buildChangeSet @ const contentText <<<<<<<<<<<<<<<<<<<<
✔ updating from 0.0.1 to 0.1.0
✔ updating from 0.1.0 to 0.1.0
❯ Fetching changelog.json from branch main
⚠ file changelog.json did not exist
❯ Fetching .release-please-manifest.json from branch main
>>>>>>>>>>>>>>>>>>>> START LOGS @ class Github.buildChangeSet @ const contentText >>>>>>>>>>>>>>>>>>>>
content: {
  sha: '82e5f33da7194d8fd2a5f3380986b58996b37232',
  mode: '100644',
  content: 'ewogICIuIjogIjAuMS4wIiwKICAicGFja2FnZXMvYSI6ICIwLjAuMSIKfQ==\n',
  parsedContent: '{\n  ".": "0.1.0",\n  "packages/a": "0.0.1"\n}'
}
contextText:  {
  ".": "0.1.0",
  "packages/a": "0.0.1"
}
<<<<<<<<<<<<<<<<<<<< END LOGS @ class Github.buildChangeSet @ const contentText <<<<<<<<<<<<<<<<<<<<
>>>>>>>>>>>>>>>>>>>> START LOGS @ class ReleasePleaseManifest.updateContent >>>>>>>>>>>>>>>>>>>>
content:  {
  ".": "0.1.0",
  "packages/a": "0.0.1"
}
this.versionsMap:  Map(1) {
  'packages/a' => Version {
    major: 0,
    minor: 1,
    patch: 0,
    preRelease: undefined,
    build: undefined
  }
}
parsed - updated:  { '.': '0.1.0', 'packages/a': '0.1.0' }
<<<<<<<<<<<<<<<<<<<< END LOGS @ class ReleasePleaseManifest.updateContent <<<<<<<<<<<<<<<<<<<<
>>>>>>>>>>>>>>>>>>>> START LOGS @ class ReleasePleaseManifest.updateContent >>>>>>>>>>>>>>>>>>>>
content:  {
  ".": "0.1.0",
  "packages/a": "0.1.0"
}
this.versionsMap:  Map(1) {
  '.' => Version {
    major: 0,
    minor: 2,
    patch: 0,
    preRelease: undefined,
    build: undefined
  }
}
parsed - updated:  { '.': '0.2.0', 'packages/a': '0.1.0' }
<<<<<<<<<<<<<<<<<<<< END LOGS @ class ReleasePleaseManifest.updateContent <<<<<<<<<<<<<<<<<<<<
>>>>>>>>>>>>>>>>>>>> START LOGS @ class ReleasePleaseManifest.updateContent >>>>>>>>>>>>>>>>>>>>
content:  {
  ".": "0.2.0",
  "packages/a": "0.1.0"
}
this.versionsMap:  Map(0) {}
parsed - updated:  { '.': '0.2.0', 'packages/a': '0.1.0' }
<<<<<<<<<<<<<<<<<<<< END LOGS @ class ReleasePleaseManifest.updateContent <<<<<<<<<<<<<<<<<<<<
❯ Fetching package-lock.json from branch main
⚠ file package-lock.json did not exist
❯ Fetching npm-shrinkwrap.json from branch main
⚠ file npm-shrinkwrap.json did not exist
❯ Fetching samples/package.json from branch main
⚠ file samples/package.json did not exist
❯ Fetching CHANGELOG.md from branch main
>>>>>>>>>>>>>>>>>>>> START LOGS @ class Github.buildChangeSet @ const contentText >>>>>>>>>>>>>>>>>>>>
content: undefined
contextText:  undefined
<<<<<<<<<<<<<<<<<<<< END LOGS @ class Github.buildChangeSet @ const contentText <<<<<<<<<<<<<<<<<<<<
❯ Fetching package.json from branch main
>>>>>>>>>>>>>>>>>>>> START LOGS @ class Github.buildChangeSet @ const contentText >>>>>>>>>>>>>>>>>>>>
content: {
  sha: 'c0e05987be5b4b714cee7869ac3bfe465b68dfe1',
  mode: '100644',
  content: 'ewogICJuYW1lIjogInJlbGVhc2UtcGxlYXNlLW1vbm9yZXBvLXdpdGgtcm9v\n' +
    'dC1leGFtcGxlIiwKICAidmVyc2lvbiI6ICIwLjEuMCIsCiAgImRlc2NyaXB0\n' +
    'aW9uIjogIiIsCiAgImxpY2Vuc2UiOiAiSVNDIgp9\n',
  parsedContent: '{\n' +
    '  "name": "release-please-monorepo-with-root-example",\n' +
    '  "version": "0.1.0",\n' +
    '  "description": "",\n' +
    '  "license": "ISC"\n' +
    '}'
}
contextText:  {
  "name": "release-please-monorepo-with-root-example",
  "version": "0.1.0",
  "description": "",
  "license": "ISC"
}
<<<<<<<<<<<<<<<<<<<< END LOGS @ class Github.buildChangeSet @ const contentText <<<<<<<<<<<<<<<<<<<<
✔ updating from 0.1.0 to 0.2.0
✔ updating from 0.2.0 to 0.2.0
  packages/a/package-lock.json:  [class PackageLockJson]
no change found for packages/a/package-lock.json
  packages/a/npm-shrinkwrap.json:  [class PackageLockJson]
no change found for packages/a/npm-shrinkwrap.json
  packages/a/samples/package.json:  [class SamplesPackageJson extends DefaultUpdater]
no change found for packages/a/samples/package.json
  packages/a/CHANGELOG.md:  [class Changelog extends DefaultUpdater]
Index: packages/a/CHANGELOG.md
===================================================================
--- packages/a/CHANGELOG.md
+++ packages/a/CHANGELOG.md
@@ -0,0 +1,8 @@
+# Changelog
+
+## [0.1.0](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/compare/a-v0.0.1...a-v0.1.0) (2024-05-15)
+
+
+### Features
+
+* **a:** some change ([00abf7d](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/commit/00abf7d7d524a75d7a52c08f72aa3eec4851074b))

  packages/a/package.json:  [class CompositeUpdater]
Index: packages/a/package.json
===================================================================
--- packages/a/package.json
+++ packages/a/package.json
@@ -1,6 +1,6 @@
 {
   "name": "a",
-  "version": "0.0.1",
+  "version": "0.1.0",
   "description": "",
   "license": "ISC"
 }
\ No newline at end of file

  changelog.json:  [class CompositeUpdater]
no change found for changelog.json
  .release-please-manifest.json:  [class CompositeUpdater]
Index: .release-please-manifest.json
===================================================================
--- .release-please-manifest.json
+++ .release-please-manifest.json
@@ -1,4 +1,4 @@
 {
-  ".": "0.1.0",
-  "packages/a": "0.0.1"
+  ".": "0.2.0",
+  "packages/a": "0.1.0"
 }
\ No newline at end of file

  package-lock.json:  [class PackageLockJson]
no change found for package-lock.json
  npm-shrinkwrap.json:  [class PackageLockJson]
no change found for npm-shrinkwrap.json
  samples/package.json:  [class SamplesPackageJson extends DefaultUpdater]
no change found for samples/package.json
  CHANGELOG.md:  [class Changelog extends DefaultUpdater]
Index: CHANGELOG.md
===================================================================
--- CHANGELOG.md
+++ CHANGELOG.md
@@ -0,0 +1,8 @@
+# Changelog
+
+## [0.2.0](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/compare/release-please-monorepo-with-root-example-v0.1.0...release-please-monorepo-with-root-example-v0.2.0) (2024-05-15)
+
+
+### Features
+
+* some change ([ef77e16](https://github.com/01Joseph-Hwang10/release-please-monorepo-with-root-example/commit/ef77e163205409883c8fd87f2d3e456d43dc3f99))

  package.json:  [class CompositeUpdater]
Index: package.json
===================================================================
--- package.json
+++ package.json
@@ -1,6 +1,6 @@
 {
   "name": "release-please-monorepo-with-root-example",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "",
   "license": "ISC"
 }
\ No newline at end of file

In this case, it appears that, in the end, only one class CompositeUpdater for .release-please-manifest.json exists.
So each update is applied sequentially, preserving every update pushed during the execution.
This seems to be happening because class Merge plugin merges every update pushed by previously executed functions and methods, which is, AFAIK, only used when there are multiple packages to release. (Correct me if I'm wrong)
# ...
updates - merged - release-please-manifest:  [
  {
    path: '.release-please-manifest.json',
    createIfMissing: false,
    updater: CompositeUpdater { updaters: [Array] }
  }
]
updates - merged - release-please-manifest - updater:  [
  CompositeUpdater {
    updaters: [ [CompositeUpdater], [ReleasePleaseManifest] ]
  }
]
<<<<<<<<<<<<<<<<<<<< END LOGS @ class Merge.run @ const updates <<<<<<<<<<<<<<<<<<<<

Happens to me too with node-workspace plugin when root package.json has more than 2 workspaces and one is not defined in packages section of release-please-config.json

I fixed this in above commit, take a look at config key separate-pull-requests - schema says it's false by default - I wonder why when I explicitly set this to false it starts to work all of a sudden? ^^ No idea but trying to find out.

Hey team, happening to us as well on a bare nodejs mono repo. Anything we can do on our side to help repro or fix the issue? Thanks

This worked for me https://github.com/wheresrhys/fetch-mock/pull/706


Typo "Azure Database for Postgres"→"Azure Database for PostgreSQL"

https://docs.microsoft.com/en-us/azure/azure-arc/data/migrate-postgresql-data-into-postgresql-hyperscale-server-group
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-arc/data/migrate-postgresql-data-into-postgresql-hyperscale-server-group.md
#PingMSFTDocs

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#sign-off


Create pypi module

so that pastepwn can be installed via pip

If possible, can I take this one?

Well, I would like to be the maintainer of the pypi module in the end - but I am glad about all the help which is needed in order to create the module.


Fix whitespace character class escape in createWordRegExp

This PR fixes a bug that affects go-to definitions and other capabilities utilising getWordAtText in src/vscodeFunctions/wordHelper.ts. Line 22 appends \s to the end of a string containing a regular expression with the intention of matching a whitespace character, but \s in a JavaScript string is a redundant escape sequence evaluating to just s. Consequently, the getWordAtText function recognises the character s as a word boundary, and not whitespace.
method Thi() { }
method I() { }
method Broken() { }
datatype MyType = ThisIsBroken

In the current version of the extension, invoking go-to-definition on ThisIsBroken will take you to one of the methods Thi, I, or Broken, depending on where exactly your cursor is.

Thanks @nhweston!


precommit npm script not running after installing minobo a second time from a fresh clone

For some reason the precommit script no longer runs after cloning the repo again.

Added documentation on how to fix this. See https://github.com/nickytonline/minobo/commit/07482a81a34401c0b0ca6cc5d7c46c20becc2ebe.

Also, see https://github.com/typicode/husky/issues/84#issuecomment-280004732


GTIN Only case ePI is not displayed.

Description:
Test name: GTIN Only case
Steps to reproduce the error:

Create a product and an associated batch. with the below settings:
Product setting:

Batch setting:

Valid details
GTIN: (01)21215242352340
Expiry: (17)210531
Batch: (10)UV2309
When the batch ID is changed, then the scenario must ideally shift to the GTIN Only case.
for example, here is a code where the batch is incorrectly encoded:

Invalid details:
GTIN: (01)21215242352340
Expiry: (17)210531
Batch: (10)UV2306
however, when the code is scanned  the application does not display the  ePI

cc @skutner @asaccool @nhrishi @salboaie

Hello @adiganga2002
Please do let us know how you are tackling this case, since this is a critical case that is widely tested.
Here are some additional inputs  that have come to light in the recent testing :
Steps to reproduce the error:

When a product with the wrong batch is scanned - the GTIN Only scenario is activated -  then we receive the below screen with the error message:

Once OK is clicked on the above screen - the next screen is displayed

Corrections to the above:
Correction 1. :
The error message must be modified:
👎 Current error message: “The batch number in the barcode cannot be found.  You are being provided with the latest leaflet”.
👍 Expected error message: "The batch number in the barcode could not be found"
Correction 2.  In the manage product screen , We need to make an update to the solution so that a company can determine if they want to display the leaflet if the Batch Number is unknown.
So we would add another check box to this list to manage the incorrect batch case

cc: @maherpa2 , @nhrishi


As data editor I want to search for footnote bibliography records by autocomplete so that I can more easily document accounts associated with the cards

testing notes
When editing an account, the card lookup should now be an autocomplete instead of a drop down. Check that you can add, remove, change cards associated with accounts.
The autocomplete doesn't restrict the list to lending library cards only, but the validation will. To confirm this, try adding a book from the bibliography (there's a google books link you can use) and then saving - you should get a validation error and not be able to save with any bibliography record that isn't a lending library card.

Like what's already there for adding footnote bibliography records
But for adding into accounts

YES, when I go to the "accounts" menu and search the card box, I don't have a dropdown menu but an autocomplete. I tried with Richard Aldington's account to add different cards and all saved!
YES, when I tried to add the googlebooks link, it wouldn't let me save


CP_SAT model Core Dumped

I was trying to solve a model using the CP_SAT solver and encountered the following error.

Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1692?email_source=notifications&email_token=ACUPL3I2DGU4ZAU5JJML4Q3QSMVJPA5CNFSM4JJ47LZ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HXLRPLA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3JWULTI4E35VH452QDQSMVJPANCNFSM4JJ47LZQ
.

Looks like you have a AddModuloEquality where the mod var's domain contains 0.

Indeed. You cannot have negative or zero modulos.
Le mer. 6 nov. 2019 à 23:31, Xiang Chen<EMAIL_ADDRESS>a écrit :

Looks like you have a AddModuloEquality where the mod var's domain
contains 0.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1692?email_source=notifications&email_token=ACUPL3J4LLGXZ7N2Z3BF7G3QSNASXA5CNFSM4JJ47LZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDIG5ZA#issuecomment-550530788,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3LGBGNKHQNBSL7HNDLQSNASXANCNFSM4JJ47LZQ
.

I believe that is what the error is about, but the modulo base that I'm using is a constant number.
@lperron Here is the model
https://gist.github.com/hktony0129/a5816f860eeb1e4e1cd10d8bbf972c16

Yes a bug on our side during presolve + expansion.
I have fixed the code. It will returns infeasible, which I hope is expected.
Thanks a lot.

Infeasible was what was expected for the model.
Thank you for fixing it in such a short time.


An unhandled exception occured when loading the SharpShell Server Types from the specified assembly

Running srm.exe install MyShellExtension.dll -codebase fails:
========================================
SharpShell - Server Registration Manager
========================================

An unhandled exception occured when loading the SharpShell
Server Types from the specified assembly. Is it a SharpShell
Server Assembly?

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at ServerRegistrationManager.Application.InstallServer(String path, RegistrationType registrationType, Boolean codeBase)
   at ServerRegistrationManager.Application.Run(String[] args)
   at ServerRegistrationManager.Program.Main(String[] args)

This seems to be because MyShellExtension.dll was built for x64 platform. It works when it is Any CPU. Does srm.exe only work with Any CPU assemblies?

If you are compiling srm yourself for any cpu, make sure to change the prefer 32 bit in properties. If you are running 64 bit os and 32 bit preferred then it will error out.
Also you can install your server with:
StartInfo(@"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe", """ + GetAssembly.AssemblyInformation("directory") + "\YOUR_SERVER.dll" + """ + " -codebase);
ofc the framework path is dependent on the framework version and whether you compiled for 32/64 bit. As far as Any CPU for your server I am not certain but it would be easy enough to try.

I used the srm.exe from from SharpShellTool nuget package.

I'm having the same issue trying to install SharePointWebDavShellExtension.
`========================================
SharpShell - Server Registration Manager
An unhandled exception occured when loading the SharpShell
Server Types from the specified assembly. Is it a SharpShell
Server Assembly?
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at ServerRegistrationManager.Application.InstallServer(String path, RegistrationType registrationType, Boolean codeBase)
at ServerRegistrationManager.Application.Run(String[] args)
at ServerRegistrationManager.Program.Main(String[] args)
SharePoint WebDav Shell Extension installed
Press any key to continue . . .`

This issue is now resolved with the latest srm tool. The latest versions have just been deployed, see:
https://github.com/dwmkerr/sharpshell/releases/tag/v2.5.3


non-overlapping rules

we need to come up with rules for communicating non-overlapping areas to the user

This is now fixed in Alternative_Compute_Results


bluetooth: Add Read Characteristic Value Changed Sample

This sample combines readValue, characteristicvaluechanged and {start,stop}Notifications to read battery level and be notified of changes from a nearby BLE device.
Featured:

characteristicvaluechanged event listener added to read characteristic value ✨
read & notifications on the same characteristic
trick to get all devices

R=@scheib @jyasskin @g-ortuno @jeffposnick
Try it live at https://beaufortfrancois.github.io/samples/web-bluetooth/read-characteristic-value-changed.html
PS: There's a bug on Android I've filed at http://crbug.com/622217

@g-ortuno feedback is addressed.
If that looks good, I'll commit once https://codereview.chromium.org/2085293002/ lands.

lgtm

Will wait on a final LGTM from @scheib before we land this.

@scheib Does that look good to you now? If so, I'll merge it.

Thanks, LGTM


Correct the optimizition of HCI event calll back in bluenrg_sdk_api.c

1.Correct the optimizition of HCI event calll back in bluenrg_sdk_api.c
2.The HCI event call back can not distinguish central or peripheral connection status.

OK


stuck with loading

**** update ****
finally got it to work, the right click "file upload" does not work, but works by the top package navigation drop down list.
This could be fixed and even a shortcut created could be nice to upload the file ^SU save and upload?

Hello, thanks for the plug-in.
I can't get it to work,
I have filled the ftp parameters and when I push the file on the remote site I get a loading icon forever.
Is there some kind of log I can look at?
I must say that I have LittelSnitch running and allowed Atom to upload on any ports, but maybe you use an alternate service that I might need to enable via my outbound  firewall
Best regards,
Patrice.

none of the steps mentioned above work for me. I, too, stuck on the loading icon.

Go to your packages folder (Win: /users/USER/.atom/packages/SFTP-Deployment) and edit the file sftp-deployment.cson located in the keymaps folder.
Replace
'.tree-view': [
        { 'type': 'separator' }
        { 'label': 'FTP/SFTP', 'submenu': [
            { 'label': 'Upload selection', 'command': 'sftp-deployment:uploadSelection' }
            { 'label': 'Download selection', 'command': 'sftp-deployment:downloadSelection' }
        ]}
        { 'type': 'separator' }
    ]```
with

'.tree-view': [
{ 'type': 'separator' }
{ 'label': 'FTP/SFTP', 'submenu': [
###{ 'label': 'Upload selection', 'command': 'sftp-deployment:uploadSelection' }###
###{ 'label': 'Download selection', 'command': 'sftp-deployment:downloadSelection' }###
{ 'label': 'Upload current file', 'command': 'sftp-deployment:uploadCurrentFile' }
{ 'label': 'Download current file', 'command': 'sftp-deployment:downloadCurrentFile' }
]}
{ 'type': 'separator' }
]```
Now you can upload files from the filetree's context menu


Health is restored when hearts are with drawn.

When the player withdraws heart, his health is restored, for example, if the player has 5 hp points with 10 max hearts, his health is restored (becomes 20 hp the max health) even if withdraws only heart.

This bug is fixed in the new update.
Modrinth
Curseforge


src/revel/revel/validation.go (195 row)

Add Validation errors to RenderArgs. (Ur code)
c.RenderArgs["errors"] = c.Validation.ErrorMap()
Mine will out all errors that will be after validation on template
c.RenderArgs["errors"] = c.Validation.Errors

Not sure what the issue is, Repopen with more info


Publish x64 version auth dll with amd64 suffix to match os.arch

Can you change arch suffix of x64 version to amd64 such that it matches ${os.arch}?
This will make usage a bit easier:
<dependency>
    <groupId>com.microsoft.sqlserver</groupId>
    <artifactId>mssql-jdbc_auth</artifactId>
    <version>11.2.0.${os.arch}</version>
    <type>dll</type>
</dependency>

Otherwise I have to have an extra maven profile to map os.arch to suffix.

Hi @mwisnicki,
We can take a look at this in our upcoming triage, but generally small-scale enhancements like this are lower priority. If we end up addressing this, we may look at making the auth.dll names configurable, such as is suggested in #1850. Outright changing the name is probably not happening.

Hey, thanks for reply. I don't think making names configurable at runtime changes anything with regard to this request as the artifact published in maven still needs to be named uniquely (unless you change how you distribute dlls).

That was also discussed as part of the issue. Regardless, we'll take a look at all of our naming at a later time.

hi @mwisnicki
ultimately we would like to get rid of the DLLs all together however we are currently blocked by issue AzureAD/microsoft-authentication-library-for-java#299. Once that's available we will be working towards moving all the DLL functionalities into the Java code so we can get rid of all the DLLs.

Will a Windows arm64 version of mssql-jdbc_auth be provided in a future release?

@lilgreenbird's comment above still stands, our next goal regarding these auth DLLs is their removal entirely, however we're still blocked by the PR mentioned above.

Out of curiosity, how does microsoft-authentication-library-for-java eliminate the need for JNI to call crypt/advapi?


Upon scroll stories break out of column and stretch infinitely to the right

E.g Go to: https://opendatabutton.org/action and scroll down to load more stories. This is on Chrome at least.

Fixing in new site

On new request pages this doesn't seem to happen. Happy to close.


BUG in inheritance to sklearn routines (e.g. cross validation, grid search) due to new get_& set_params

Occurs for FQK and PQK.
The kernel instance is missing arguments due to inheritance issues.
from sklearn.model_selection import cross_val_score
from squlearn.kernel.ml import QSVR
q_kernel_svr = FidelityKernel(
    feature_map=fmap, executor=Executor("statevector_simulator"), parameter_seed=0)
qsvr = QSVR(quantum_kernel=q_kernel_svr)
cross_val_score(qsvr, X_train.reshape(-1, 1), Y_train, cv=5)

---------------------------------------------------------------------------
...

Results in TypeError: FidelityKernel.__init__() missing 2 required positional arguments: 'feature_map' and 'executor'

Solved in pull request #107


[SR-2679] Fix for URLSession delivers redirection delegate methods in wrong order

Thanks. The implementation looks good to me.
But it took me a while to understand the control flow related to the added test. Seems like the initial in-process HTTP server (HTTPServer.swift) is no longer good enough for the kind of tests that we are adding. There is some work happening on improving/refactoring the loopback server. Until that is available, this test is OK, but we'd need to improve upon it thereafter ;-)

@swift-ci please test


BUG: Fix possible nil excpetion

Fix possible nil exception at setDataSource and setDelegate

How can we proceed and merge this fix? It definitely fixes crashes related to setting nil delegate.


TODO: Application: VMModule: Inject HyperVM

Closed by https://github.com/CityOfZion/neo-sharp/pull/503