Skip to content

Merge from upstream v2.42.2 - #263

Merged
1ec5 merged 545 commits into
stagingfrom
1ec5-merge-v2.42.2
Oct 27, 2026
Merged

1ec5 merged 545 commits into
stagingfrom
1ec5-merge-v2.42.2

Conversation

@1ec5

@1ec5 1ec5 commented Oct 12, 2026

Copy link
Copy Markdown
Member

Merged the upstream v2.42.2 tag into the latest OHM staging branch. Upstream is undergoing a piecemeal conversion from JavaScript to TypeScript, introducing merge conflicts that needed more manual review.

tyrasd and others added 30 commits June 15, 2026 14:24
…map#12448)

Bumps the types group with 1 update: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node).


Updates `@types/node` from 25.9.1 to 25.9.2
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-version: 25.9.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: types
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [esbuild](https://github.com/evanw/esbuild) from 0.28.0 to 0.28.1.
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.28.0...v0.28.1)

---
updated-dependencies:
- dependency-name: esbuild
  dependency-version: 0.28.1
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ap#12412)

landuse=plant_nursery is more similar to landuse=orchard and
landuse=vineyard (cultivated agricultural areas) than to natural
vegetation like forest/grass. This moves it to the 'Light Green
things' group so it renders with a lighter green/yellowish color.
…nstreetmap#12452)

Bumps the eslint group with 1 update: [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint).


Updates `typescript-eslint` from 8.60.1 to 8.61.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.61.0/packages/typescript-eslint)

---
updated-dependencies:
- dependency-name: typescript-eslint
  dependency-version: 8.61.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: eslint
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…le (openstreetmap#12453)

* Apply a proper intended logic fix for openstreetmap#12129 / openstreetmap#12128
* add test to check intersection-prevention algorithm

---------

Co-authored-by: Martin Raifer <martin@raifer.tech>
…map#8724

when multiple primary tags are presence, and only the non-highway one is implying oneway-ness.

e.g. for `highway=track + piste:type=downhill` the oneway only applies to the piste sense of the feature, not when interpreted as a highway.
* Add track grade-based styling
* Change track styling to be based on grade-only (and not surface)
* Increase track casing color lightness slightly
* Tweak unpaved roads, bridges and tunnels

---------

Co-authored-by: Martin Raifer <martin@raifer.tech>
…map#12406)

* Fix uiField not considering sub-tags for multiCombo fields
* Fix uiField revert and isModified functions not considering prior matching tags for multiCombo
* Add tests for multiCombo field modified checks and undo operation
* Add tests for multiCombo field remove operation
…enstreetmap#12467

fixes a crash when hovering over another way while cancelling the drawing of a new way, when the other way has a field that relies on correct contents in `context.selectedIDs`, which are then still containing the outdated reference to the then cancelled way entity
@1ec5 1ec5 added the upstream label Oct 12, 2026
@netlify

This comment was marked as outdated.

Comment thread dist/iD.js
Comment thread scripts/update_imagery.js
Comment on lines 7 to +15
/** @type {import("geojson").FeatureCollection} */
const sources = JSON.parse(
fs.readFileSync(require.resolve('ohm-editor-layer-index/imagery.json'), 'utf8')
fs.readFileSync(require.resolve('@openstreetmap/editor-layer-index/imagery.geojson'), 'utf8')
);
/** @type {import("geojson").FeatureCollection} */
const ohmSources = JSON.parse(
fs.readFileSync(require.resolve('ohm-editor-layer-index/imagery.geojson'), 'utf8')
);
sources.features.push(...ohmSources.features);

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mradamcox and I think we haven’t been running this script for many releases, if we’ve ever run it. As it was, the script would clobber any upstream imagery in favor of ohm-editor-layer-index build products (which are out of date with respect to the repository’s main branch). Since there was a merge conflict here, I wound up accepting both to combine both upstream and downstream repositories together. This only works because the downstream was eviscerated early on to serve as an overlay of sorts. If we redo that repository to be a more typical fork, then we would need to revisit this code. Either way, we’ll need to rebuild that repository’s build products to reflect the last couple years of PRs merged.

Comment thread .cspell/custom-dictionary.txt
@netlify

This comment was marked as outdated.

@1ec5

1ec5 commented Oct 20, 2026 •

Copy link
Copy Markdown
Member Author

Netlify doesn’t seem to associate the deployment with the OHM account there. I would’ve expected the subdomain to reference OHM instead of a randomized slug.

Edit: Ah OK, that’s just the Netlify comment. Maybe we can customize that. But the GitHub deployment action also links to https://pr-263--ideditor.netlify.app/ instead of https://pr-263--openhistoricalmap-ideditor.netlify.app/.

@1ec5

This comment was marked as resolved.

@1ec5

This comment was marked as resolved.

@mradamcox

Copy link
Copy Markdown

Ah OK, that’s just the Netlify comment.

This comment comes from the deployment I made from my own netlify account actually, the glistening-truffle site, sorry I mucked things up--totally didn't understand the other deploy was running from github actions. So currently there are two different builds going on: mine and the one that is triggered by the workflow, that one being hosted at https://openhistoricalmap-ideditor.netlify (with deploy previews prefixed pr-<pr number>--).

I think I should just fully delete my deploy, right? Then we'll be back to having the single workflow deployment for previews, but I don't think that integration will provide us with comments on PRs like you see above.

@1ec5

1ec5 commented Oct 20, 2026 •

Copy link
Copy Markdown
Member Author

Correct, all we’ll get is a GitHub deployment event like #263 (comment) and the “branch was successfully deployed” box below.

@mradamcox

mradamcox commented Oct 20, 2026 •

Copy link
Copy Markdown

Ah, interesting, so that comment comes from this script,

environment_url: `https://pr-${pr}--ideditor.netlify.app`,

which is run as the final step in the deploy preview workflow:

const { afterDeploy } = await import('${{github.workspace}}/scripts/pr_preview.js');

and, as you can see, the original netlify id is hard-coded in there. That's why the "View deployment" button goes to the wrong site.

@mradamcox

mradamcox commented Oct 20, 2026 •

Copy link
Copy Markdown

So I'm going to go ahead and delete my Netlify integration, and then on your end you can update that pr_preview.js line to be openhistoricalmap-ideditor.netlify.app. Then when you commit and push, we'll see what the preview rebuild and comment look like.

@1ec5

1ec5 commented Oct 20, 2026

Copy link
Copy Markdown
Member Author

OK, the latest deployment status is still busted, but I think that’s only because we haven’t merged this PR yet. Otherwise, can y’all take https://pr-263--openhistoricalmap-ideditor.netlify.app/ for a spin before we merge? Thanks!

@1ec5
1ec5 requested review from k-yle and mradamcox October 20, 2026 21:04
Comment thread modules/presets/field.ts

_this.title = () => {
// @ts-expect-error -- blocked by OHM-specific id-tagging-schema
if (field.index) {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

source:1 and source:2 look a bit broken. will take a look. other than that, it seems to work well

Image

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3a7b61f has my fix, I commited it to a separate branch for now. Once we've setup the OHM-specific id-tagging-schema, we won't need this code anyway

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, #258 removed similar code in favor of resolving stringsCrossReference slightly later on, in an attempt to make it more data-driven. We can pull in your fix though; whatever works in the short term.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@k-yle are you able to cherry-pick that commit to this branch? If not, I'd say we should complete this merge and then you can make a quick branch just to snag that commit (I know @1ec5 is traveling this week).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, done. this LGTM to me now

@mradamcox mradamcox left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great guys, so sorry I missed this review request last week and held us up. Let's do it!

@mradamcox
mradamcox requested a review from k-yle October 26, 2026 15:27
Comment thread modules/presets/field.ts

_this.title = () => {
// @ts-expect-error -- blocked by OHM-specific id-tagging-schema
if (field.index) {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, done. this LGTM to me now

@1ec5
1ec5 merged commit 7319fde into staging Oct 27, 2026
9 checks passed
@1ec5
1ec5 deleted the 1ec5-merge-v2.42.2 branch October 27, 2026 14:08

This branch was successfully deployed

1 active deployment
pr-preview-263 — 3a7b61ff Deployed Oct 27, 2026 by github-actions[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.