Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG][vscode-extension] 404 on Changelog Release Notes Link

Open
#1,964 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
typescript, vscode

Research direction

Search the repository for the Salesforce Code Analyzer Release Notes URL ending in .md and identify where the VSCode extension's changelog link is defined. Replace the broken target with the reported .html URL, then verify that the link from both the Visual Studio Marketplace changelog and VSCode resolves successfully.

Written by the indexing model from the issue text.

Description

Have you tried to resolve this issue yourself first?
  • I confirm I have gone through the above steps and still have an issue to report.
Bug Description

The changelog link that opens in both the visual studio marketplace site and on VSCode is leading to a 404.

Output / Logs

Steps To Reproduce
  1. Navigate to https://marketplace.visualstudio.com/items/salesforce.sfdx-code-analyzer-vscode/changelog or click on "CHANGELOG" on VSCode
  2. Click on the Salesforce Code Analyzer Release Notes link.
  3. 404 on this page
Expected Behavior

I think the link should be: https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/release-notes.html (.html instead of .md)

Operating System

macOS

Visual Studio Code Version

latest

Extension Version

latest

Salesforce CLI Version

@salesforce/cli/2.114.5 darwin-arm64 node-v24.1.0

Code Analyzer CLI Plugin Version

No response

Node Version

No response

Java Version

No response

Python Version

No response

Additional Context (Screenshots, Files, etc)

No response

Workaround

No response

Urgency

Low

Dominant language
TypeScript
Stars
240
Forks
52
Avg merge
9h 48m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from forcedotcom/code-analyzer

All issues in forcedotcom/code-analyzer

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.