[pull] main from sparklemotion:main #3

pull · 2021-10-22T18:24:46Z

See Commits and Changes for more details.

Can you help keep this open source service alive? 💖 Please sponsor : )

google-cla · 2021-10-22T18:25:21Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-10-23T18:01:27Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-10-23T18:02:11Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-10-23T20:12:28Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-10-26T17:19:36Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-10-27T19:08:01Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-10-28T15:02:45Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-03T17:33:15Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-03T17:34:30Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-06T16:47:05Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-06T16:47:29Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T21:11:27Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-15T14:05:37Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-15T14:06:26Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-15T18:56:52Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-15T18:58:12Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[skip ci]

- xmlGetActualEncoding is an internal-only libxml2 function which we can't use (yet?) - the ctxt->input->encoding bit is no longer needed as of libxml 2.12 [skip ci]

**What problem is this PR intended to solve?** I'm about to do some work on the sax parser encoding functionality, so let's clean this file up.

"it's" means "it is", "its" means "belonging to it"

We'll use this in an upcoming commit to simplify the sax parsers

and polyfill xmlSwitchEncodingName. We'll need this functionality in the next commit.

Previously, encoding overrides were not implemented for XML::SAX::Parser#parse_memory (as reported in #918) and XML::SAX::Parser#parse_file. However, this commit goes further and significantly simplifies and unifies the two SAX::ParserContext implementations and the two SAX::Parser implementations. This commit also allows Encoding objects and encoding names to be passed into the SAX::ParserContext methods, and the XML memory and file methods now accept and properly use passed encodings. Finally, this commit also backfills a lot of test coverage for the XML and the HTML4 sax parser encoding. Closes #918

**What problem is this PR intended to solve?** Previously, encoding overrides were not implemented for XML::SAX::Parser#parse_memory (as reported in #918) and XML::SAX::Parser#parse_file. However, this commit goes further and significantly simplifies and unifies the two SAX::ParserContext implementations and the two SAX::Parser implementations. This commit also allows Encoding objects and encoding names to be passed into the SAX::ParserContext methods, and the XML memory and file methods now accept and properly use passed encodings. Finally, this commit also backfills a lot of test coverage for the XML and the HTML4 sax parser encoding. Closes #918 **Have you included adequate test coverage?** Yes. **Does this change affect the behavior of either the C or the Java implementations?** Yes, but they are more consistent with each other.

Updates the requirements on [standard](https://github.com/standardrb/standard) to permit the latest version. - [Release notes](https://github.com/standardrb/standard/releases) - [Changelog](https://github.com/standardrb/standard/blob/main/CHANGELOG.md) - [Commits](standardrb/standard@v1.39.0...v1.39.1) --- updated-dependencies: - dependency-name: standard dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>

…3289)

…3416)

and replace the .cross_rubies file with misc/native.yml

**What problem is this PR intended to solve?** Update to rake-compiler-dock v1.9.1 and replace the .cross_rubies file with misc/native.yml

[skip ci]

**What problem is this PR intended to solve?** Improvements to doc for XML::ParseOptions. **Have you included adequate test coverage?** N/A. All doc. **Does this change affect the behavior of either the C or the Java implementations?** No. --------- Co-authored-by: Mike Dalessio <[email protected]>

**What problem is this PR intended to solve?** Clarifies the far-reaching importance of XML::Node. **Have you included adequate test coverage?** Doc only. **Does this change affect the behavior of either the C or the Java implementations?** Doc only.

[skip ci]

fixes #3432

Updates the requirements on [standard](https://github.com/standardrb/standard) to permit the latest version. - [Release notes](https://github.com/standardrb/standard/releases) - [Changelog](https://github.com/standardrb/standard/blob/main/CHANGELOG.md) - [Commits](standardrb/standard@v1.44.0...v1.45.0) --- updated-dependencies: - dependency-name: standard dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>

…3434)

Updates the requirements on [rubocop-minitest](https://github.com/rubocop/rubocop-minitest) to permit the latest version. - [Release notes](https://github.com/rubocop/rubocop-minitest/releases) - [Changelog](https://github.com/rubocop/rubocop-minitest/blob/master/CHANGELOG.md) - [Commits](rubocop/rubocop-minitest@v0.36.0...v0.37.0) --- updated-dependencies: - dependency-name: rubocop-minitest dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>

and some other small fixes

**What problem is this PR intended to solve?** Fixes #3432 **Have you included adequate test coverage?** Not applicable here? **Does this change affect the behavior of either the C or the Java implementations?** Seems like it does not.

[skip ci]

….37.0 (#3435)

https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.13.6

I had thought to put in an Issue for this, but instead will make bold and propose to `:nodoc:` `Node#accept`. Reason: I was unable to find out how I would use this (so maybe it should be internal?). I found nothing in `test`, and on the wide web, saw only that accept/visit often have to do with data locking. If this is to be retained as user documentation, I'd like to be able to document it properly, but would need help (pointers to relevant docs both within `nokogiri` and elsewhere).

**What problem is this PR intended to solve?** Forward-port #3437 to `main`.

…3447) Implements part of [Issue 3439](#3439). --------- Co-authored-by: Mike Dalessio <[email protected]>

Fixes #3455

**What problem is this PR intended to solve?** In this PR, I've updated `Node#namespace_definitions` to no longer use the namespace cache, meaning it uses the attributes defined on the node to determine the return value(s). Removing this use of the cache revealed a separate bug in the `relink_namespace` java function, which suddenly became better tested on JRuby as a result of removing the cache usage (which was hiding the bug). Finally, removing the cache also means that `relink_namespace` now needs to remove namespace definitions that are redundant (that is, the exact prefix and URI resolve in the parent) in order to match the CRuby implementation, so I've done that, too. Closes #2543 **Have you included adequate test coverage?** Yes. **Does this change affect the behavior of either the C or the Java implementations?** Only the Java implementation, which now behaves like the CRuby implementation (and I've resolved a pending JRuby test).

so that pending_if displays the right frame

so that nodes can be built that rely on namespaces they define. Fixes #3458

**What problem is this PR intended to solve?** Simplify Builder to do late binding on namespaces, so that nodes can be built that rely on namespaces they define. Fixes #3458 **Have you included adequate test coverage?** Existing pending coverage (now resolved) is sufficient. **Does this change affect the behavior of either the C or the Java implementations?** This really only affects the CRuby implementation, which now behaves like the JRuby impl does.

pull bot added the ⤵️ pull label Oct 22, 2021

flavorjones and others added 13 commits July 6, 2024 16:09

doc: update CHANGELOG

f9b2661

[skip ci]

doc: xml_sax_parser.c comments

f582d6b

- xmlGetActualEncoding is an internal-only libxml2 function which we can't use (yet?) - the ctxt->input->encoding bit is no longer needed as of libxml 2.12 [skip ci]

tidy: update html4/sax/test_parser.rb to use minitest::spec

e145889

tidy: update html4/sax/test_parser.rb to use minitest::spec (#3285)

3062700

**What problem is this PR intended to solve?** I'm about to do some work on the sax parser encoding functionality, so let's clean this file up.

tidy: update test/*/sax/test_parser_context.rb to use minitest::spec

28680f5

doc: correct "it's" to "its" as the possessive pronoun

1a93c71

"it's" means "it is", "its" means "belonging to it"

feat: ClassResolver can find related classes in SAX namespaces

a3c4ce2

We'll use this in an upcoming commit to simplify the sax parsers

ext(libxml): intro noko_xml_sax_parser_context_set_encoding()

a887af9

and polyfill xmlSwitchEncodingName. We'll need this functionality in the next commit.

doc: update CHANGELOG with "notable changes" for v1.17

f67b294

build(deps-dev): update standard requirement from 1.39.0 to 1.39.1 (#…

77d6be9

…3289)

flavorjones and others added 30 commits January 20, 2025 09:50

build(deps-dev): update standard requirement from 1.43.0 to 1.44.0 (#…

53ecfd4

…3416)

dep: update to rake-compiler-dock v1.9.1

0994b4e

and replace the .cross_rubies file with misc/native.yml

dep: update to rake-compiler-dock v1.9.1 (#3418)

b2bf25d

**What problem is this PR intended to solve?** Update to rake-compiler-dock v1.9.1 and replace the .cross_rubies file with misc/native.yml

doc: update CHANGELOG

6830270

[skip ci]

dep: update rdoc

d5d64bb

[skip ci]

[DOC] :nodoc: for Node#accept

200e60d

Drop Struct::HTMLElementDescription class

6c4afc5

fixes #3432

build(deps-dev): update standard requirement from 1.44.0 to 1.45.0 (#…

26db10c

…3434)

style: remove the "global" minitest assertion style

d326ef2

and some other small fixes

Drop Struct::HTMLElementDescription class (#3433)

527e28f

**What problem is this PR intended to solve?** Fixes #3432 **Have you included adequate test coverage?** Not applicable here? **Does this change affect the behavior of either the C or the Java implementations?** Seems like it does not.

doc: update CHANGELOG

c11e91c

[skip ci]

build(deps-dev): update rubocop-minitest requirement from 0.36.0 to 0…

640d8d1

….37.0 (#3435)

dep: update libxml2 to v2.13.6

832a94f

https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.13.6

doc: update CHANGELOG with v1.18.x releases

f63c0df

ci: update alpine docker image with yaml-dev

94b7926

ci: tired of waiting for gnome mirrors

4374b2b

dep: update libxml2 to v2.13.6 (main branch) (#3438)

130b173

**What problem is this PR intended to solve?** Forward-port #3437 to `main`.

In XML::ParseOptions.rb put :nodoc: onto constants SAX1 and NODICT (#…

6ae2f19

…3447) Implements part of [Issue 3439](#3439). --------- Co-authored-by: Mike Dalessio <[email protected]>

[skip ci] Add links to local pages in README.md (#3449)

85df710

Fix MRI Ruby vs. JRuby XML child namespace output differences (#3456)

babd976

Fixes #3455

fix(java): stop using the cache for Node#namespace_definitions

691a0f3

dev: improve the pending test helper

ecfeec5

so that pending_if displays the right frame

fix: simplify Builder to do late binding on namespaces

2c0c85d

so that nodes can be built that rely on namespaces they define. Fixes #3458

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[pull] main from sparklemotion:main #3

[pull] main from sparklemotion:main #3

pull bot commented Oct 22, 2021 •

edited

Loading

google-cla bot commented Oct 22, 2021

google-cla bot commented Oct 23, 2021

google-cla bot commented Oct 23, 2021

google-cla bot commented Oct 23, 2021

google-cla bot commented Oct 26, 2021

google-cla bot commented Oct 27, 2021

google-cla bot commented Oct 28, 2021

google-cla bot commented Nov 3, 2021

google-cla bot commented Nov 3, 2021

google-cla bot commented Nov 6, 2021

google-cla bot commented Nov 6, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 15, 2021

google-cla bot commented Nov 15, 2021

google-cla bot commented Nov 15, 2021

google-cla bot commented Nov 15, 2021

[pull] main from sparklemotion:main #3

Are you sure you want to change the base?

[pull] main from sparklemotion:main #3

Conversation

pull bot commented Oct 22, 2021 • edited Loading

google-cla bot commented Oct 22, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Oct 23, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Oct 23, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Oct 23, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Oct 26, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Oct 27, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Oct 28, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 3, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 3, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 6, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 6, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 15, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 15, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 15, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 15, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

pull bot commented Oct 22, 2021 •

edited

Loading