Skip to content

Commit b29bd2f

Browse files
authored
v1.6.0 Release Preparations (#48)
* update to v1.6.0 * Udpate changelog * update readme with contributing section * added CONTRIBUTING.md * added CODE_OF_CONDUCT.md * update gh actions * .vscodeignore updates * added known issue with update install Signed-off-by: Jens Reinecke <jens.reinecke@arm.com>
1 parent 14c74a1 commit b29bd2f

7 files changed

Lines changed: 147 additions & 14 deletions

File tree

.github/workflows/ci.yml

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -16,10 +16,10 @@ jobs:
1616
name: Build
1717
runs-on: ubuntu-latest
1818
steps:
19-
- uses: actions/checkout@v3
19+
- uses: actions/checkout@v4
2020
with:
2121
fetch-depth: 0
22-
- uses: actions/setup-node@v3
22+
- uses: actions/setup-node@v4
2323
with:
2424
node-version: 14.x
2525
- name: Build
@@ -29,7 +29,7 @@ jobs:
2929
yarn install --ignore-scripts
3030
yarn build
3131
yarn package
32-
- uses: actions/upload-artifact@v3
32+
- uses: actions/upload-artifact@v4
3333
with:
3434
name: vsix-package
3535
path: ./*.vsix
@@ -43,11 +43,11 @@ jobs:
4343
contents: write
4444
if: startsWith(github.ref, 'refs/tags/')
4545
steps:
46-
- uses: actions/checkout@v3
47-
- uses: actions/download-artifact@v3
46+
- uses: actions/checkout@v4
47+
- uses: actions/download-artifact@v4
4848
with:
4949
path: artifacts
50-
- uses: softprops/action-gh-release@v1
50+
- uses: softprops/action-gh-release@v2
5151
with:
5252
files: artifacts/*/*.vsix
5353

@@ -57,11 +57,11 @@ jobs:
5757
runs-on: ubuntu-latest
5858
if: startsWith(github.ref, 'refs/tags/')
5959
steps:
60-
- uses: actions/checkout@v3
61-
- uses: actions/download-artifact@v3
60+
- uses: actions/checkout@v4
61+
- uses: actions/download-artifact@v4
6262
with:
6363
path: artifacts
64-
- uses: actions/setup-node@v3
64+
- uses: actions/setup-node@v4
6565
with:
6666
node-version: 14.x
6767
- name: Publish
@@ -74,11 +74,11 @@ jobs:
7474
runs-on: ubuntu-latest
7575
if: startsWith(github.ref, 'refs/tags/')
7676
steps:
77-
- uses: actions/checkout@v3
78-
- uses: actions/download-artifact@v3
77+
- uses: actions/checkout@v4
78+
- uses: actions/download-artifact@v4
7979
with:
8080
path: artifacts
81-
- uses: actions/setup-node@v3
81+
- uses: actions/setup-node@v4
8282
with:
8383
node-version: 14.x
8484
- name: Publish

.vscodeignore

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,10 @@
1+
.eslintignore
12
.github
3+
.gitignore
24
.vscode
35
node_modules
46
src
7+
tsconfig.json
58
*.vsix
69
!node_modules/@vscode/codicons/dist/codicon.css
710
!node_modules/@vscode/codicons/dist/codicon.ttf

CHANGELOG.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,25 @@
11
# Change Log
22

3+
## [v1.6.0] - 2025-02-06
4+
5+
### New Features
6+
7+
- Allow use of Peripheral Inspector in SSH remote scenario. ([Rob Moran](https://github.com/thegecko)).
8+
- Updated Peripheral Inspector to use [Ant Design](https://ant.design/docs/react/introduce/) React UI library ([Haydar Metin](https://github.com/haydar-metin), [Martin Fleck](https://github.com/martin-fleck-at), and others)
9+
- Added `Export Registers` functionality ([QuocTrung76](https://github.com/QuocTrung76))
10+
- Added `Search` functionality ([Martin Fleck](https://github.com/martin-fleck-at))
11+
- Added `Peripheral-inspector: Ignore Peripherals` extension setting to hide peripherals and skip reading their registers. Also added context menu entries to add and clear the setting on workspace level from the Peripheral Inspector view ([Haydar Metin](https://github.com/haydar-metin))
12+
13+
### Other Changes
14+
15+
- Updated extension logo.
16+
17+
### Known Issue
18+
19+
- As a side effect of moving to a custom Webview implementation, the Peripheral Inspector may show the following message when launched after update from a previous version:<br>
20+
`There is no data provider registered that can provide view data.`<br>
21+
***Solution***: Please restart your IDE after the update installation to overcome this problem. Restarting the extension may not be sufficient.
22+
323
## [v1.5.1] - 2023-12-13
424

525
### Bug Fixes

CODE_OF_CONDUCT.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
2+
3+
<div id="theia-logo" align="left">
4+
<br />
5+
<img src="https://raw.githubusercontent.com/eclipse-theia/theia/master/logo/EF_GRY-OR_svg.svg?sanitize=true" alt="Eclipse Logo" width="300"/>
6+
</div>
7+
8+
# Community Code of Conduct
9+
Version 1.0
10+
June 23, 2015
11+
12+
As members of the Eclipse community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting code reviews, pull requests, patches, and other activities.
13+
14+
We are committed to making participation in the Eclipse community a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion or analogous grounds.
15+
16+
Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
17+
18+
Eclipse Foundation staff have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. Project leaders, committers and contributors who do not follow the Code of Conduct may be removed from the project.
19+
20+
This code of conduct applies within Eclipse project spaces, or in public spaces when an individual is representing the project or the Eclipse community.
21+
22+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by emailing the Eclipse Management Organization: codeofconduct@eclipse.org.
23+
24+
This Code of Conduct is adapted from the Contributor Covenant (http://contributor-covenant.org), version 1.1.0, available at http://contributor-covenant.org/version/1/1/0/
25+
26+
27+
<div id="theia-logo" align="left">
28+
<br />
29+
<img src="https://www.eclipse.org/images/Eclipse_Code_of_Conduct.png" alt="Eclipse Logo" width="150"/>
30+
</div>
31+
32+
----
33+
Note: Please see [here](https://www.eclipse.org/org/documents/Community_Code_of_Conduct.php) for the latest version of this document, hosted at the Eclipse Foundation

CONTRIBUTING.md

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
# Contributing to Eclipse CDT Cloud Peripheral Inspector
2+
3+
This repository is the home to the CDT Cloud Peripheral Inspector.
4+
5+
## How Can I Contribute?
6+
7+
In the following some of the typical ways of contribution are described.
8+
9+
### Asking Questions
10+
11+
It's totally fine to ask questions by opening an issue in the
12+
[GitHub repository](https://github.com/eclipse-cdt-cloud/vscode-peripheral-inspector).
13+
We will close it once it's answered and tag it with the 'question' label.
14+
Please check if the question has been asked before.
15+
16+
### Reporting Bugs
17+
18+
If you have found a bug, you should first check if it has already been filed
19+
and maybe even fixed in the
20+
[issues](https://github.com/eclipse-cdt-cloud/vscode-peripheral-inspector/issues).
21+
If you find an existing unresolved issue, please add your case. If you could not
22+
find an existing bug report, please
23+
[file a new one](https://github.com/eclipse-cdt-cloud/vscode-peripheral-inspector/issues/new/choose).
24+
In any case, please add all information you can share and that will help to
25+
reproduce and solve the problem.
26+
27+
### Reporting Feature Requests
28+
29+
You may want to see a feature or have an idea. You can
30+
[file a request](https://github.com/eclipse-cdt-cloud/vscode-peripheral-inspector/issues/new/choose)
31+
and we can discuss it. If such a feature request already exists, please add a comment
32+
or some other form of feedback to indicate you are interested, too. Also in this
33+
case any concrete use case scenario is appreciated to understand the motivation
34+
behind it.
35+
36+
### Pull Requests
37+
38+
Before you get started investing significant time in something you want to get
39+
merged and maintained as part of this project, you should talk with the team
40+
by posting on an issue. Simply choose the issue you would want to work on, and tell everyone
41+
that you are willing to do so and how you would approach it. The team will be
42+
happy to guide you and give feedback.
43+
44+
## Eclipse Contributor Agreement
45+
46+
Before your contribution can be accepted by the project team contributors must
47+
electronically sign the Eclipse Contributor Agreement (ECA).
48+
49+
* http://www.eclipse.org/legal/ECA.php
50+
51+
Commits that are provided by non-committers must have a Signed-off-by field in
52+
the footer indicating that the author is aware of the terms by which the
53+
contribution has been provided to the project. The non-committer must
54+
additionally have an Eclipse Foundation account and must have a signed Eclipse
55+
Contributor Agreement (ECA) on file.
56+
57+
For more information, please see the Eclipse Committer Handbook:
58+
https://www.eclipse.org/projects/handbook/#resources-commit
59+
60+
## Sign your work
61+
62+
The sign-off is a simple line at the end of the explanation for the patch. Your
63+
signature certifies that you wrote the patch or otherwise have the right to
64+
pass it on as an open-source patch.
65+
66+
Signed-off-by: Joe Smith <joe.smith@email.com>
67+
68+
Use your real name (sorry, no pseudonyms or anonymous contributions.)
69+
70+
If you set your `user.name` and `user.email` git configs, you can sign your
71+
commit automatically with `git commit -s`.

README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -101,3 +101,9 @@ Additionally the following settings can be used to customize the Peripheral Insp
101101

102102
- `peripheral-inspector.saveLayout`- Save layout of peripheral view between sessions (default: `true`)
103103
- `peripheral-inspector.ignorePeripherals` - List of peripheral names to ignore. They will not show up in the tree view and no values are read from the target system. The user can add variables by using the context menu (**Workspace only**) in the tree view, or by setting them manually in the **User** and **Workspace** preferences.
104+
105+
## Contributing
106+
107+
We welcome contributions on [GitHub](https://github.com/eclipse-cdt-cloud/vscode-peripheral-inspector).
108+
Check our [contribution guidelines](./CONTRIBUTING.md) for more info.
109+
This open-source project is part of [Eclipse CDT Cloud](https://eclipse.dev/cdt-cloud/).

package.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
"name": "peripheral-inspector",
33
"displayName": "Peripheral Inspector",
44
"description": "Standalone Peripheral Inspector extension extracted from cortex-debug",
5-
"version": "1.5.1",
5+
"version": "1.6.0",
66
"publisher": "eclipse-cdt",
77
"author": "marus25",
88
"contributors": [
@@ -350,4 +350,4 @@
350350
"workspace",
351351
"ui"
352352
]
353-
}
353+
}

0 commit comments

Comments
 (0)