Reviewing files that changed from the base of the PR and between 7abea7a and ce28995.

• README.md (1 hunks)
• holidays/constants.py (1 hunks)
• holidays/countries/north_macedonia.py (3 hunks)
• holidays/locale/en_US/LC_MESSAGES/MK.po (1 hunks)
• holidays/locale/mk/LC_MESSAGES/MK.po (1 hunks)
• holidays/locale/uk/LC_MESSAGES/MK.po (1 hunks)
• snapshots/countries/MK_COMMON.json (1 hunks)
• tests/countries/test_north_macedonia.py (1 hunks)

holidays/constants.py (1)

60-67: Global holiday category constants added.
The new constants (ALBANIAN, ARMENIAN, BOSNIAN, ROMA, SERBIAN, TURKISH, VLACH) are introduced alphabetically and follow the existing lowercase naming convention. Please ensure these categories are consumed by the North Macedonia country class’s supported_categories list.

README.md (1)

966-967: README updated for North Macedonia.
The “Supported Languages” and “Supported Categories” columns now correctly list en_US, mk, uk and the expanded holiday categories (ALBANIAN, BOSNIAN, CATHOLIC, HEBREW, ISLAMIC, ORTHODOX, ROMA, SERBIAN, TURKISH, VLACH), matching the code changes in constants and locale files.

holidays/locale/en_US/LC_MESSAGES/MK.po (1)

1-148: New English localization file appears complete.
All msgstr entries are populated appropriately, and header metadata (Project-Id-Version, language, creation date) is correct. No untranslated strings detected.

holidays/locale/uk/LC_MESSAGES/MK.po (1)

1-148: Ukrainian localization added successfully.
The msgstr entries are fully populated with accurate Ukrainian translations, including status annotations (приблизна дата) and (вихідний). Header metadata is in order.

snapshots/countries/MK_COMMON.json (1)

1-15: Verify snapshot language consistency with new default mk.

The snapshot still stores English labels while NorthMacedonia.default_language is now "mk".
Double-check that the snapshot generator is explicitly instantiated with language="en_US"; otherwise, the CI “snapshot compare” step may start failing.
No action needed if the generator already forces the locale.

holidays/countries/north_macedonia.py (1)

264-303:

❓ Verification inconclusive

Extend fixed Islamic date tables beyond 2025.

Static mappings stop at 2025, yet the module serves data to 2050.
After 2025 every Eid is flagged estimated, sacrificing accuracy.
If authoritative dates are available, pre-populate the tables:

+    2029: (APR, 24),
+    2030: (APR, 13),
+    # … up to 2050

Apply the same treatment to EID_AL_FITR_DATES.

---

Extend static Islamic holiday mappings through 2050

The NorthMacedoniaIslamicHolidays class currently hard-codes Eid al-Adha and Eid al-Fitr only up to 2025; after that the library falls back to estimated dates. If you have authoritative dates through 2050, please add them to improve accuracy.

• File: holidays/countries/north_macedonia.py
Lines: 264–303

Suggested diff format:

 class NorthMacedoniaIslamicHolidays(_CustomIslamicHolidays):
     EID_AL_ADHA_DATES = {
         …,
         2025: (JUN, 6),
+        2026: (MAY, 27),
+        2027: (MAY, 17),
+        2028: (MAY, 6),
+        2029: (APR, 24),
+        # … continue through 2050
     }

     EID_AL_FITR_DATES = {
         …,
         2025: (MAR, 30),
+        2026: (MAR, 20),
+        2027: (MAR, 10),
+        2028: (FEB, 27),
+        2029: (FEB, 16),
+        # … continue through 2050
     }

Please confirm you have reliable sources for the post-2025 dates before merging.

tests/countries/test_north_macedonia.py (1)

110-112: range() objects may not be what assertHolidayName expects.

Several assertions pass range(...) directly (e.g. range(2007, 2050)).
Unless the helper expands those integers into concrete ISO-date strings, the comparison is effectively no-op.
Please verify and, if needed, replace with an explicit generator:

(f"{year}-04-20" for year in range(2007, 2050))